Geographic management system

ABSTRACT

A geographic management system (GMS) comprises a web server, a database server, and a map server. A user browser connected to the GMS transmits a search criteria to the web server. The web server transmits the search criteria to the map server. The map server geocodes the search criteria, obtains network data and geospatial data from the database server corresponding to the geocode, and transmits the geocode, the network data, and the geospatial data to the web server. The web server transmits the geocode, the network data, and the geospatial data to the user browser. The network data and the geospatial data are displayed on the user browser as a map displaying network elements of a telecommunication network relative to other network elements, geographic elements, and customers. One or more of the network elements have associated performance elements or sectored performance elements that display performance characteristics or sectored performance characteristics that signify performance attributes associated with the network element. The user browser can navigate through other network data and geospatial data by selecting network elements on the map or by selecting navigation tools or navigation tabs displayed in conjunction with the map.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.10/004,346, filed on Nov. 1, 2001 now U.S. Pat. No. 7,447,509, entitledGeographic Management System which was a continuation-in-part of U.S.patent application Ser. No. 09/470,553, filed on Dec. 22, 1999, entitledGeographic Network Management System, now U.S. Pat. No. 6,343,290, allof which are incorporated fully herein.

FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not Applicable

COMPACT DISK APPENDIX

Not Applicable

BACKGROUND OF THE INVENTION

The present invention relates to the field of network configuration andmanagement using geographic data and network data.

Managing wireline and wireless networks has become increasinglydifficult. Service providers now connect calls for digital wirelesscommunications and/or analog wireless communications (“wirelesscommunications”) and/or wireline communications. The service providersmust provide expansive coverage, adequate capacity, high reliability,and quality customer service to be competitive in the market and to meetconsumer needs. As used herein, the terms “customer” and “consumer” areused synonymously to mean a subscriber of a telecommunication servicefrom a telecommunication service provider. An example of a customer is aperson or a company subscribing to (i.e. purchasing) wireless telephoneservice from a wireless telephone service provider. Therefore, a systemis needed to view, configure, and manage wireline and wireless networksand to provide network data to a user of the system in a context thatmakes the network data useful and efficient for viewing, configuration,and management.

SUMMARY OF THE INVENTION

Systems and methods are used to manage a network using a processor. Inone embodiment, the systems and methods are configured to generatedisplay elements comprising geographic elements each having at least onegeographic characteristic, network elements each having at least onenetwork characteristic, and performance elements each having at leastone performance characteristic. Each performance characteristiccorresponds to a performance attribute, and each performance element isgenerated for display for at least one network element.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a geographic management system inaccordance with an embodiment of the present invention.

FIG. 2 is a diagram of network elements and geographic elements in atelecommunication system in accordance with an embodiment of the presentinvention.

FIG. 3 is a block diagram of an expanded geographic management system inaccordance with an embodiment of the present invention.

FIG. 4 is a block diagram of an expanded geographic management system inaccordance with an embodiment of the present invention.

FIG. 5A is a diagram of network elements and geographic elements in atelecommunication system for a screen display in accordance with anembodiment of the present invention.

FIG. 5B is a diagram of network elements, geographic elements, andsectored performance elements in a telecommunication system for a screendisplay in accordance with an embodiment of the present invention.

FIG. 5C is a diagram of network elements, geographic elements, andsectored performance elements for a rubber-band zoom in atelecommunication system for a screen display in accordance with anembodiment of the present invention.

FIG. 6 is a block diagram of an orientation of a geographic managementsystem in accordance with an embodiment of the present invention.

FIG. 7A is a block diagram of an orientation of a geographic managementsystem in accordance with an embodiment of the present invention.

FIG. 7B is a block diagram of an orientation of a redundant geographicmanagement system in accordance with an embodiment of the presentinvention.

FIG. 8 is a block diagram of a graphical interface of a geographicmanagement system in accordance with an embodiment of the presentinvention.

FIG. 9 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 10 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 11 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 12 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 13 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 14 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 15 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 16 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 17 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 18 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 19 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 20 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 21 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 22A is a screen view of a screen in accordance with an embodimentof the present invention.

FIG. 22B is a screen view of a screen in accordance with an embodimentof the present invention.

FIG. 23 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 24 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 25 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 26 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 27 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 28 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 29 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 30 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 31 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 32 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 33 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 34 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 35 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 36 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 37 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 38 and FIG. 39 are screen views of screens in accordance with anembodiment of the present invention.

FIG. 40 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 41 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 42 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 43 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 44 is a screen view of a screen in accordance with an embodiment ofthe present invention.

FIG. 45A is a screen view of a screen in accordance with an embodimentof the present invention.

FIG. 45B is a screen view of a screen in accordance with an embodimentof the present invention.

DETAILED DESCRIPTION

The present invention provides a system for managing one or morenetworks. As used herein, the term “network” may identify one or moredifferent types of geographic areas in which one or more types of dataare to be depicted. For example, a network may include an oil or gasindustry network configured to identify one or more oil wells. Also, anetwork may include a communication network or a store network.

The present invention may be configured to manage networks using networkdata and geospatial data to provide a geographical representation of anetwork through a graphical interface for a user. The system is used toview, monitor, configure, and manage networks. As used herein, networkdata comprises performance data, equipment data, performance data,including trouble ticket data, event data, alarm data, customer servicedata, and/or configuration data for calls, for network elements, and/orfor performance elements.

A trouble ticket is an entry of data for a reported problem in service.For example, a customer may call customer service of a service providerto report that the customer's call has been dropped. The customerservice user then enters data regarding the customer or the call,including the geographic location of the customer and the call and theservice problem, such as a trouble ticket. Service problems may include,among others, blocked calls, dropped calls, fast busy, unspecified, orothers. As used herein, geospatial data comprises geographic data and/orspatial data. Geographic data includes location data comprising dataidentifying latitude, longitude, addresses, city, state, county,streets, street crossings, and/or other location data. Spatial datacomprises data of or representing geographic elements, including streetsor highways, streams, lakes, other bodies of water, parks, mountains,terrain, land marks, structures, and/or other geographic identificationdata, including image data and/or text data.

The present invention can be used to display network elements, with orwithout performance elements, relative to each other, relative tocustomers, and relative to geographic elements. This allows users of theinvention to provide factual, data-based feedback to customers. Forexample, a user can inform a customer that a cell site is notoperational or that trouble areas are existent and known and when theservice will be restored.

FIG. 1 illustrates an exemplary embodiment of the management system 102of the present invention. The management system 102 comprises ageographic management system (GMS) 104 communicating with a user 106 andone or more network elements 108 and 110.

The GMS 104 receives and stores network data. Typically, the GMS 104 hasgeospatial data or can receive and store geospatial data. The GMS 104organizes the network data and the geospatial data to be output to auser, when needed, in a context that allows the user readily to view,monitor, configure, and manage the network data and the networkelements. The GMS 104 generates data for display of network data withrelation to the geospatial data to illustrate the physical locations ofnetwork elements and associated performance elements, geographicelements, and customers in a telecommunication system, configuresnetwork data and geospatial data for respective network elements andgeographic elements in a telecommunication system, configuresperformance parameters and operational parameters and componentsassociated with network elements, and manages network data andperformance and operational parameters and components associated withnetwork elements.

In addition to providing configuration of network elements, the GMS 104tracks and manages trouble tickets, trouble areas, and performance ofnetwork elements for a telecommunication network. A user of the GMS 104may enter trouble tickets for problems reported by customers. The useralso may select one or more trouble tickets to close when the problem isresolved. The GMS 104 can be configured to transmit explanations ofproblem resolutions to customers by, for example, an email, a textpager, an automated voice response, a voice mail, or other transmissionmechanisms. This notification serves to build customer loyalty.

The GMS 104 automatically creates customer defined “trouble areas” whena new trouble ticket is created within a specified range of a specifiednumber of other trouble tickets. The range and the number can be definedby a user or pre-set. In addition, the GMS 104 allows entry of anengineer defined or user defined trouble area. The engineer defined/userdefined trouble area is a known trouble area whose problem, parameters,and perimeters are defined and described by an engineer or another user.A script describing the problem of the trouble area or the anticipatedresolution of the problem may be entered by an engineer or another user.If a new trouble ticket is entered for the trouble area, the script willbe displayed to the user so the resolution explanation can be relayed tothe customer. The defined trouble area is depicted on a geographicdisplay to the user.

The user 106 is hardware or software that communicates with the GMS 104.The user 106 transmits and receives network data and geospatial data toand from the GMS 104. The user 106 has a display that displays thenetwork data and the geospatial data in a graphical display. Therefore,the user 106 displays the network elements and other network data,including trouble tickets, the geographic elements, and any definedareas, such as customer defined trouble areas or known engineer definedtrouble areas.

The network elements 108 and 110 comprise a cell site, an element of acell site, such as an antenna, a base transceiver, or a switch, such asa local exchange carrier (LEC) switch, an interexchange carrier (IXC)switch, or a tandem switch, a wireline circuit, a wireless circuit, aphone, a service platform, a legacy based information system, a networkdata supplier, or any other device or medium capable of transmitting orreceiving communications or signaling, including network data andgeospatial data, to or from the GMS 104. A service platform can be, forexample, a computer platform capable of processing calls. Examples ofservice platforms include operator services platforms, directoryassistance platforms, prepaid call processing platforms, voice mailplatforms, and digital service unit platforms.

FIG. 2 illustrates an exemplary embodiment of a telecommunication system202 having network elements and geographic elements with network dataand geospatial data for which network elements may be viewed, monitored,configured, and managed. FIG. 2 illustrates network elements relative totheir respective physical locations and relative to geographic elementsand customers in a geographic location of a telecommunication network202. The telecommunication network 202 of FIG. 2 comprises cell sites204-212, switches 214-216, another network element 218, wirelinecircuits 220-224, and a wireless circuit 226. Trouble tickets 228-236are depicted relative to the telecommunication network 202 with itsnetwork elements 204-226 and relative to geographic elements in ageographic location of the telecommunication network, such as majorroads 238-250, minor or other roads 252-260, a land mark 262, a stream264, and a park 266. For simplicity, not all network elements capable ofbeing in the telecommunication network 202 are depicted in FIG. 2. Thoseskilled in the art will appreciate that different network elements, morenetwork elements, or fewer network elements may be included in thetelecommunication network. Likewise, not all geographic elements capableof being in a geographic location of the telecommunication network 202are depicted in FIG. 2. Those skilled in the art will appreciate thatdifferent geographic elements, more geographic elements, or fewergeographic elements may be included in the geographic location.

The management system 102 of FIG. 1 operates as follows. A user 106connects to the GMS 104 and logs into the GMS. The user 106 may enter asearch criteria, such as a base transceiver station (BTS) event, anaddress, an intersection, a trouble ticket, a major trading area, or acell site, to obtain a map display of an area or a telecommunicationnetwork. The map is generated by the GMS 104 and includes anidentification of the network elements, such as cell sites, othernetwork data, such as trouble ticket data, and geographic elements, suchas streets and streams within a search range. The user 106 may selectone of the network elements, such as a cell site or a trouble ticket.This action will initiate a process to populate network data for theselected cell or trouble ticket.

Based upon the search criteria entered by the user and the selection onthe generated map, network data is output for one or more of a cell andcell status, a trouble ticket and trouble ticket problem type, cell siteinformation, specific trouble ticket data, event and alarm data for cellsites and trouble tickets, and network statistics. In addition, the user106 has the ability to identify and specify high traffic or high troubleareas.

The user can use the display as a mechanism to enter configurationinformation for the selected network element or for a new networkelement. Other capabilities and embodiments of the GMS 104 are describedmore fully below.

FIG. 3 illustrates an exemplary embodiment of a GMS 104A in a managementsystem 102A of the present invention. The GMS 104A comprises acommunication system 302, a data management system 304, and a geospatialsystem 306. The GMS 104A is in communication with the user 106 and thenetwork element 108. The term “system” means software and/or hardwarethat may be implemented as one or more components. Thus, thecommunication system 302, the data management system 304, and thegeospatial system 306 represent logical components that are scalable andthat may be implemented as software and/or hardware individually, as asingle component, or as multiple components.

The communication system 302 receives and processes communications, suchas queries and data, from the data management system 304 and thegeospatial system 306. The communication system 302 transmitscommunications, such as queries and data, to the data management system304 and the geospatial system 306. The communication system 302 receivesimages and text information of geospatial data from the geospatialsystem 306 and receives network data from the data management system304.

The communication system 302 transmits communications to, and receivescommunications from, the user 106. The communications include dataand/or signaling. The communication system 302 may obtain the data orsignaling from the data management system 304 and/or the geospatialsystem 306. The communication system 302 processes communicationsreceived from the user 106, including network data for network elementconfiguration and management and other data, and, if necessary,communicates the processed network data to the data management system304 or the geospatial system 306. The communication system 302materializes a graphical interface to the user 106.

The data management system 304 receives and processes communications,such as queries and data, from the communication system 302 and thegeospatial system 306. The data management system 304 transmitscommunications, such as queries and data, to the communication system302 and the geospatial system 306. The data management system 304retrieves data from, or stores data in, an associated database (notshown).

The geospatial system 306 receives and processes communications,including queries and data, from the communication system 302 and thedata management system 304. The geospatial system 306 transmitscommunications, including queries and data, to the communication system302 and the data management system 304. The geospatial system 306communicates with the data management system 304 to obtain geospatialdata. The geospatial system 306 identifies and generates a geocode, suchas a latitude and longitude, for a search criteria, identifies networkelements and any associated performance elements and geographic elementslocated within a search range of the search criteria, and generatesimages and text representing the identified network elements, anyassociated performance elements, and the identified geographic elements.The images and/or the text are displayed as a map.

As used herein, generating a map also can be construed to meangenerating data and/or signaling to be used by the user 106 to display amap, depending on context. Likewise, generating geospatial data, networkdata, or geographic data also can be construed to mean generating datato be used by the user 106 to display the geospatial data, network data,or geographic data, depending on context. Similarly generating networkelements, performance elements, geographic elements, or data thereof,display elements, or display characteristics also can be construed tomean generating data and/or signaling to be used by the user 106 todisplay the network elements, performance elements, geographic elements,or data thereof, display elements, or display characteristics, dependingon context. Thus, generating any data also means generating data and/orsignaling to be used by the user 106 to display representations of thedata, depending on context. The term transmitting and other like termsused to describe any communication transmitted or received by anyelement or component of a telecommunication system, including the GMS,is used in a similar manner herein.

The GMS 104A of FIG. 3 operates as follows. The user 106 transmits asearch criteria to the communication system 302 in a communication. Thecommunication system 302 processes the search criteria and transmits thesearch criteria to the geospatial system 306. The geospatial system 306geocodes the search criteria, obtains network data and geospatial datafrom the data management system 304 corresponding to the geocode, andtransmits the geocode, the network data, and the geospatial data to thecommunication system 302. The communication system 302 transmits thegeocode, the network data, and the geospatial data to the user 106. Thenetwork data and the geospatial data are displayed for the user 106 as amap displaying network elements of a telecommunication network relativeto other network elements, geographic elements, and customers. Thenetwork elements may have associated performance elements, as describedmore fully below. The map also displays coverage areas, trouble areas,and layers of network data, including the display characteristics fornetwork elements, performance elements, and geographic elements.

The user 106 navigates through other network data and geospatial data byselecting network elements on the displayed map or by using navigationtools. Additional communications are sent to the communication system302 identifying the selections. The communication system 302 processesthe communications, obtains network data and geospatial data from thegeospatial system 306 or the data management system 304 and transmitsthe network data and the geospatial data to the user 106. In addition,the user can enter network data to configure parameters or components ofnetwork elements. This network data is transmitted in a communication tothe communication system 302 for implementation and/or storage by thedata management system 304. The network data and the geospatial datainclude, for example, performance data, statistical data, event data,configuration data, management data, geocode data, geographic data, andother data. In this manner, the user 106 can view, monitor, manage, andconfigure network data for network elements.

FIG. 4 illustrates an exemplary embodiment of a GMS 104B of the presentinvention. The GMS 104B comprises a web server 402, a database server404, a network data database 406, a geospatial data database 408, a mapserver 410, a geocode generator 412, and a map generator 414. The GMS104B communicates with a network element, such as a data supplier 416,via a connection or link and a user browser 418 via a connection orlink, such as an internet protocol (IP) connection 420. The term“server” means software and/or hardware that may be implemented as oneor more components. Thus, the web server 402, the database server 404,and the map server 410 represent logical components that are scalableand that may be implemented as software and/or hardware individually, asa single component, or as multiple components.

The web server 402 transmits and receives communications, includingnetwork data, geospatial data, and other data, to and from the userbrowser 418 and processes communications. The web server 402communicates with the user browser in any applicable format or protocol.The web server 402 materializes a graphical interface, such as thegraphical interface described below, to the user browser 418.

Preferably, the web server 402 is configured to communicate with theuser browser 418 using pages. A page may comprise one or more ofportions of code, programming, data, or other elements using any webbased technology. For example, a page can be generated using hypertextmarkup language (HTML), dynamic HTML (DHTML), Java, and/or Java Script.In this configuration, the web server 402 receives pages from the userbrowser 418 and transmits pages to the user browser. The pages maycontain network data, geospatial data, or other data. Pages received bythe web server 402 may contain search criteria, queries, data entry,including network data or geospatial data, and other data. Otherconfigurations of pages may be used.

The web server 402 also communicates with the database server 404 andthe map server 410. The web server 402 processes communications receivedfrom the user browser 418 and transmits data received from the userbrowser 418 to the database server 404 or the map server 410. The webserver 402 receives geospatial data, including images and text listinformation, from the map server 410 and receives network data from thedatabase server 404.

The database server 404 receives and processes communications, such asqueries and data, from the web server 402 and the map server 410. Thedatabase server 404 also transmits communications, including networkdata and geospatial data, to the web server 402 and the map server 410.The database server 404 receives and stores network data and geospatialdata in, or retrieves and transmits network data and geospatial datafrom, the network data database 406 and the geospatial data database408.

The database server 404 also receives data, including geospatial dataand network data, from network elements, such as the data supplier 416.The database server 404 stores the data in the network data database 406or the geospatial data database 408.

In some configurations, the database server 404 is configured to receivedata from the data supplier 416 in a documented format so that the datacan be stored directly in the network data database 406 or thegeospatial data database 408 by the database server without the databaseserver having to specially format the data. Examples of a documentedformat include a flat file or a documented format from a message bus oranother source. Other documented formats may be used. In otherconfigurations, the database server 404 is configured to receive rawdata, to process the raw data to a storage format, and to store theformatted data in the network data database 406 or the geospatial datadatabase 408. The database server 404 can be configured with anapplication interface to facilitate communication between the databaseserver 404 and the data supplier 416, if needed.

The network data database 406 is a collection of network data stored involatile or nonvolatile memory and structured and organized forefficient access. This may include one or more related databases.Volatile or nonvolatile memory may include disk storage, persistentstorage, random access memory, and other accessible memory.

The geospatial data database 408 is a collection of geospatial datastored in volatile or nonvolatile memory and structured and organizedfor efficient access. This may include one or more related databases.Volatile or nonvolatile memory may include disk storage, persistentstorage, random access memory, and other accessible memory.

The map server 410 receives and processes communications, such asqueries and data, from the web server 402 and the database server 404.The map server 410 transmits communications, such as queries and data,to the web server 402 and the database server 404. The map server 410communicates with the database server 404 to obtain geospatial data andnetwork data. The map server 410 communicates processed geospatial dataand network data to the web server 402.

The geocode generator 412 identifies and generates a geocode, such as alatitude and a longitude, based on a search criteria. Alternately, thegeocode generator 412 can be configured to identify and generate othergeocodes, such as a location identifier that designates a geographiclocation, based on a search criteria. Examples of other locationidentifiers are latitude and longitude coordinates, north, south, east,west, up, down, left, right, vertical and horizontal coordinates, NorthAmerican data (NAD) 27, NAD 83, axial coordinates, other ordinatesystems, positioning indicators, and mark identifiers.

The map generator 414 identifies network elements and geographicelements located within a search range of a geocode and generates a maphaving images and/or text representing the identified network elements,including any associated performance elements, and the identifiedgeographic elements. The map may display multiple layers of networkdata, including trouble tickets, network trouble areas, network alarms,network performance, switch configuration, coverage levels, celllocations, and future cell sites in their proper geographic location.Other layers may exist that may be used to understand the network dataand the geographic data.

For example, the map generator 414 may generate a map having componentssuch as those depicted in FIG. 2, as well as other data, or the map ofFIG. 5A described more fully below. The map may have network data and/orgeospatial data that identifies customers (e.g. by trouble tickets) in atelecommunication network relative to network elements, including anyassociated performance elements, geographic elements, and/or geographiclocations. The map generator 414 generates a map based a navigationcriteria, such as a selection of pan, zoom, or movement of a map in adirection. Direction may be specified in any form including north,south, east, west, up, down, left, right, vertical and horizontalcoordinates, latitude and longitude coordinates, NAD 27, NAD 83, inaxial coordinates, or in another ordinate system. Another example of agenerated map is the map of FIG. 5A, as described more fully below.

The data supplier 416 communicates network data to the GMS 104B. Thedata supplier 416 also may be configured to communicate geospatial datato the GMS 104B. The data supplier 416 may be a single system, a systemwith sub-systems, or a multi-system or multi-component system havingsoftware and/or hardware. For example, the data supplier 120 may includea system that collects network statistics or data for network events, asystem that catalogues network events, a trouble management system thattracks customer service data, or any system that collects or has networkdata or geospatial data. The data supplier 120 may include a proprietarycomputer from a telecommunication service provider, such as a wirelesstelephone service provider.

The user browser 418 is any software or hardware that can be used tonavigate and access data. Preferably, a browser is a tool used tonavigate and access web based information. In one example, the browseris an IP based browser that may use the hypertext transfer protocol(HTTP) to communicate with IP based systems over a connection or link.HTTP is a protocol for transferring pages or other documents from aprocessor to a browser across an intranet or internet. Preferably, theuser browser 418 is an IP based browser that communicates with the webserver 402 and provides the ability to access and transfer network dataand geospatial data via pages. Examples of browsers include theMicrosoft Internet Explorer brand browser and the Netscape Navigatorbrand browser.

A user uses the user browser 418 to view network data and geospatialdata. A user navigates through network data and geospatial data andselects network elements to “drill down”, i.e. to navigate, to anotherscreen or to display another portion of a screen having otherinformation for the selected network element or data. For example, auser may select a cell site on a display to see the status of the cellsite.

A user may enter configuration data for network elements via the userbrowser 418. The configuration data is transmitted in a communication tothe web server 402 and saved in the GMS 104B for implementation. Forexample, the user may enter configuration data for a parameter of anetwork element or a component of the network element. In this manner, auser may configure parameters or components for switches, cell sites, orother network elements, provision wireline and wireless circuits, andprovide other configuration.

The connection 420 is any connection supporting transmission ofcommunications between the web server 402 and the user browser 418.Preferably, the connection 420 is an IP connection.

As used herein, generating a map also can be construed to meangenerating data and/or signaling to be used by the user browser 418 todisplay a map, depending on context. Likewise, generating geospatialdata, network data, or geographic data also can be construed to meangenerating data to be used by the user browser 418 to display thegeospatial data, network data, or geographic data, depending on context.Similarly generating network elements, performance elements, geographicelements, or data thereof, display elements, or display characteristicsalso can be construed to mean generating data and/or signaling to beused by the user browser 418 to display the network elements,performance elements, geographic elements, or data thereof, displayelements, or display characteristics, depending on context. Thus,generating any data also means generating data and/or signaling to beused by the user browser 418 to display the data or representations ofthe data, depending on context. The term transmitting and other liketerms used to describe any communication transmitted or received by anyelement or component of a telecommunication system, including the GMS,is used in a similar manner herein.

Each of the embodiments of the GMS described herein combinesfunctionalities for defining and enabling data layers for viewing,configuration, and management of data with a presentation of servicecoverage data and network data. These functionalities provide a user theability to access significant amounts of data for easy viewing and todrill down to more levels of data and more detailed data.

The data layers are levels of network data and/or geographic data. Thedata layers, when enabled, build on each other to present data in amanner analogous to transparencies each having a portion of data thatbuilds on other data to present a more complete view of the data. One ormore of the data layers can enabled or disabled to display, configure,and manage selected data on a user-by-user basis. For example, severaldata layers may be used to present network data for network elements toan engineer, and other data layers may be used to present other networkdata to a customer service person.

The data layers present network data in a context of geographic data forcomparative analysis. This type of comparative analysis and presentationof network data in a geographic context allows a user to more easilyunderstand the data and more quickly view large amounts of data.

Some of the network data and some of the geographic data are displayedas one or more display elements, including a network element, aperformance element, or a geographic element. When displayed on adisplay, each of the network element, the performance element, and thegeographic element has at least one display characteristic. The displaycharacteristics are colors, patterns, shapes, text, symbols, or othercharacteristics that serve to distinguish levels of coverage,performance, network events, configured parameters, configuredcomponents, other network data, or geographic data for a network elementor a geographic element. The display characteristic may beuser-configurable in certain instances, as described more fully below.

The display characteristics for the performance elements are referred toas performance characteristics. The performance characteristics for theperformance elements are displayed if performance attributes occur forperformance levels. Some performance levels are user configurable, whileother performance levels are pre-configured. Each of these concepts aredescribed more fully below.

The display characteristics for the network elements are referred to asevent characteristics. The event characteristics for the networkelements are displayed if event attributes or performance attributesoccur for event levels. Some event levels are user configurable, whileother event levels are pre-configured. Each of these concepts aredescribed more fully below.

The display characteristics for the geographic elements are referred toas geographic characteristics. Various geographic characteristics aredisplayed for geographic elements, such as color, size, and shape.

Data layers may be associated with different network elements. Datalayers that are associated with cell sites may include, among others, anetwork element layer, an alarm layer, and a performance layer. Otherlayers associated with network data or with geographic data aredescribed more fully below.

The network element layer displays network elements in one of twodisplay characteristics, such as colors or patterns, depending on thestatus of the network element, event attributes, and performanceattributes. For example, one color or pattern can indicate a healthynetwork element, and a second color or pattern can indicate a warningcondition, a critical condition, or other condition for the networkelement. In another example, a cell can be displayed with a firstdisplay characteristic, such as a green color, to signify the cell siteis on-air or displayed with a second display characteristic, such as agray color, to signify that the cell site is a future cell site. Otherdisplay elements or display characteristics may be used.

An alarm layer displays network elements with multiple varied displaycharacteristics, such as multiple colors or patterns, to indicate variedevent attributes, events, event levels, degrees of event levels, orperformance attributes for a network element. For example, a cell can bedisplayed with a display characteristic, such as a green color, tosignify the cell site is not in a warning state or an alarm state, witha second display characteristic, such as a yellow color, to signify thatthe displayed cell site is in a warning state, and with a third displaycharacteristic, such as a red color, to signify that the displayed cellsite is in an alarm state. Other display elements or displaycharacteristics may be used. The display characteristics for the networkelements are referred to as event characteristics.

A performance layer displays network elements with associatedperformance elements. This allows a user to view, for example, an alarmstatus of a network element and/or a performance status of the networkelement at the same time. Alternately, the performance layer can beconfigured to display only the performance elements.

A network element can be displayed with varied display characteristics,such as colors or patterns, to signify event characteristics. Aperformance element associated with the network element can be displayedwith varied display elements, such as colors or patterns, to signifyperformance levels or performance attributes of the network element. Forexample, a cell site can be displayed with a display characteristic,such as a green color, to signify the cell site is not in a warningstate or an alarm state, with a second display characteristic, such as ayellow color, to signify that the cell site is in a warning state, andwith a third display characteristic, such as a red color, to signifythat the cell site is in an alarm state. A performance element for thecell site can be displayed having a first display characteristic, suchas a green color, to signify that the cell site does not have a warninglevel or a critical level, with a second display characteristic, such asa yellow color, to signify that the cell site has a warning level, andwith a third display characteristic, such as a red color, to signifythat the cell site has a critical level. Other display elements ordisplay characteristics may be used. The display characteristics for theperformance elements are referred to as performance characteristics. Thedisplay characteristics for the network elements are referred to asevent characteristics.

The warning state and the alarm state for events typically are not userconfigurable. An event (also referred to as an event attribute) can bedescribed as a failure, failed condition, or degradation of some networkelement, such as a circuit, a switch, or an SS7, link. A warning statemay be pre-configured as a state in which an event occurred within aselected period of time. An alarm state may be pre-configured as a statein which a current event is occurring. Because these events aresignificant in a telecommunication network, a user may not have theknowledge and expertise necessary to configure the propercharacteristics that would cause a warning state or an alarm state foran event associated with a network element. Although, in someembodiments the warning state and the alarm state may beuser-configurable. Other states may exist or may be configured or shown.

The warning level (as opposed to the warning state for events) and thecritical level are based on user configurable performance levels. Thus,a user can specify performance attributes, levels of performanceattributes, or network events that will effect the warning level, thecritical level, or another level causing display of a performanceelement. Other display elements or display characteristics may be used.

The performance element can be displayed in a form that allows a user toview the performance levels of network elements easily. Examples ofperformance elements having performance characteristics are displayelements having colors or patterns that signify configured parameters,performance attributes, or network events or other display elements,such as text or symbols, that identify configured parameters,performance attributes, or network events. For example, one or moredifferent shapes may be displayed proximal to the network element tosignify one or more performance levels or performance attributes, ashape having more than one display characteristic, such as multiplecolors, can be displayed concentrically or proximal to a networkelement, or the same shape as the network element may be displayed otherthan concentrically. Alternately, the network element can have multipledisplay characteristics, such as one display characteristic for theperformance characteristic and another display characteristic for theevent characteristic. For example, the left half of a circle candesignate the performance characteristic of a cell, and the right halfof a circle could designate the event characteristic of the cell. Inanother example, different shapes are located proximal to the networkelement to designate a performance characteristic or a network event,such as a flag, an exclamation point, a star, or a octagon. The shapesmay be color coded or have other display characteristics. Other methodsmay be used.

Preferably, a performance element is a shape displayed concentricallyaround the display element representing the network element, theconcentric shape being color coded to signify different performancelevels for performance attributes. For example, if a performance layeris enabled, a circle can be displayed as the performance elementconcentrically around a circle representing a cell. The performancelayer can be configured to display the concentric circle with aperformance characteristic, such as a color of green, a yellow color, ora red color for one or more performance attributes or performancelevels. Other display elements and other display characteristics may beused.

Performance levels of performance attributes can be configured by a userto determine how a performance element is displayed, if at all. Forexample, performance levels may be configured for attempts, drops,blocks, percent drops, percent blocks, channel erlangs, or otherperformance attributes. If one or more performance attributes reaches aconfigured performance level, a performance element is displayed on witha performance characteristic configured to signify that performancelevel.

As an example, a user can configure the GMS to display a concentriccircle as a performance element and having a yellow color as theperformance characteristic when a warning level of one hundred droppedcalls is reached. Likewise, a user can configure the GMS to display aconcentric circle as a performance element and having a red color as theperformance characteristic when a critical level of five hundred droppedcalls is reached. Other examples, other configurations, and otherperformance attributes may be used.

The system can be configured to use a logical operator to determinewhether or not to display a performance element or to determine whichperformance characteristic to display. In one example, the system can beconfigured to “and” or “or” one or more performance attributes todetermine if a performance level is reached for displaying a performanceelement. In this example, a performance level is configured for X numberof drops “and” Y number of blocks. Thus, a performance element will bedisplayed if both X number of drops and Y number of blocks occurs.Alternately, the system can be configured to display a performanceelement if either X number of drops “or” Y number of blocks occurs.

Another data layer is a coverage layer. The coverage layer identifiesgeographical areas of a telecommunication network that have variedlevels of telecommunications service, such as excellent coverage, goodcoverage, average coverage, or poor coverage. Alternately, the coveragelayer can identify whether a customer, i.e. a customer at a location, isinside a service area or outside a service area. Other levels of serviceor other methods of identifying coverage may be used.

Coverage can be identified using coverage elements, such as color-codedareas, pattern generated areas, coordinate or other ordinate identifiedareas, or areas encompassed within or outside of a circle area, apolygonal area, or another shaped area. Other coverage elements may beused. For example, a map may be generated with an area color coded ingreen to depict a good level of service covering that area. Multiplecolors may be used to depict different levels of service. Alternately,an area may be color coded with two colors-one color depicting thatservice exists for that area and another depicting that service does notexists for that area.

FIG. 5A depicts an example of a map generated by the GMS 104B. The mapincludes display elements, such as network elements, performanceelements, and geographic elements. Some of the network elements includeevent characteristics that signify event levels of network events. Theperformance elements include performance characteristics signifyingperformance levels of performance attributes. Different levels ofcoverage areas, engineering defined trouble areas, and customer definedtrouble areas also can be provided. In the example of FIG. 5A, the map502 comprises cells 504-512, performance elements 514-522 in the form ofconcentric circles, switches 524-528, a network element 530, a wirelesscircuit 532, wireline circuits 534-540, trouble tickets 542-550, alandmark 552, a customer defined trouble area 554, an engineeringdefined trouble area 556, and coverage areas 558 and 560.

The cells 504-512 each have an event characteristic that signifies anevent level of one or more event attributes. A different pattern is usedin the example of FIG. 5A as the event characteristic to distinguishbetween different event levels. Although, other event characteristicsmay be used to distinguish between event levels, such as color codes.For example, the cells 504 and 510 include an angled cross-hatchedpattern signifying that the cells are healthy and that no network eventshave occurred. The cell 512 includes a horizontal line pattern tosignify the cell is in a warning condition for one or more networkevents associated with a cell. The cells 506 and 508 include ahorizontal and vertical criss-cross pattern to signify a critical levelfor one or more network events associated with that cell.

The performance elements display performance characteristics thatsignify a performance level of one or more performance attributes. Forexample, the performance element 520 has a left to right striped patternto signify that the performance level is healthy and does not arise to awarning level or a critical level. The performance elements 514 and 516have a vertical striped pattern to signify a warning level of one ormore performance attributes associated with the respective cells 504 and506. The performance elements 508 and 512 have a right to left stripedpattern to signify a critical level of one or more performanceattributes associated with the respective cells 508 and 512. Theperformance attributes include configurable levels for a warning level,a critical level, or other specified levels for attributes including oneor more of attempts, drops, blocks, percent drops, percent blocks, andchannel erlangs. It will be appreciated that other patterns and otherperformance characteristics can be used, including color codes.

The customer defined trouble area 554 may be generated when X number oftrouble tickets occurs in a Y range of an area. For example, a customerdefined trouble area may be defined if one or more trouble ticketsoccurs within a radius, a vertical/horizontal range, alongitude/latitude range, a distance, an area defined by dimensions, oranother range. In the example of FIG. 5A, a customer defined troublearea occurs where four trouble tickets 542-548 occur within apredetermined radius. The customer defined trouble area surrounds thecells 506 and 508. Note that a user viewing the screen readily canidentify that both cells 506 and 508 are in a current event failure ordegradation, as specified by the event characteristic of the cells. Inaddition the cell 506 has a warning level for its performance level, andthe cell 508 has a critical level for its performance level. By viewingthis information, a user can easily determine network event problems andnetwork performance problems in the area of the identified troubleticket and, if needed, can describe the problem to a customer.

The engineering defined trouble area 556 is an area specified by anengineer or other authorized user as having a known problem, such aspoor service. The user can enter an associated script describing theoutage or service problem for the trouble area. If a customer calls toreport a problem for a trouble ticket 550, a user of the system can tellthe customer that the area is a known trouble area, the problemassociated with the trouble area, the time and/or date of resolution ofthe problem, and/or a description of the resolution.

In the example of FIG. 5A, the engineering defined trouble area 556encompasses the cell 512. A user readily can determine that a networkevent that is associated with the cell 512 has occurred within aspecified period of time, such as 72 hours, because of the pattern ofthe event characteristic of the cell. In addition a user can determinethat the cell has one or more critical levels of performance attributesdue to the performance characteristic of the performance element 522.

The coverage areas 558 and 560 identify levels of service coverage. Thecoverage areas 558 and 560 can be color coded, shaded, or identified byanother display characteristic so that a user can distinguish betweendifferent levels of coverage, including excellent, good, average, orpoor. In the example of FIG. 5A, the coverage area 558 is defined ashaving excellent coverage, and the coverage area 560 is defined ashaving poor coverage. The areas not specifically identified can beshaded or can be generically identified as having good coverage, anotherlevel of coverage, or as having some coverage.

A user can view parameters, components, or network elements and canconfigure parameters, components, or network elements by enteringnetwork data associated with the parameters, components, or networkelements. This is exemplified where the switch 524 is a first provider,and the switches 526 and 528 are a second provider. An interruption ofservice occurs between the switches 524 and 528. The GMS 104B allows theuser to view network data associated with the wire line circuits 536 and538 to determine where the interruption of service or other problem hasoccurred. Thus, network data for the end points of a circuit and networkdata associated with the service providers can be displayed to the user.In this example, the user determines that the interruption of service isassociated with the wireline circuit 536. A user can enter a work orderto be issued to the appropriate service provider for repair of thewireline circuit 536. In some embodiments, the user may enterconfiguration data for the wireline circuit 536 to fix the interruptionof service.

With reference to FIGS. 4 and 5, the management system 102B operates asfollows. In a first example, the connection 402 is an IP connection, andthe web server 402 and the user browser 418 communicate using the HTTPprotocol. The web server 402 and the user browser 418 transmit andreceive network data and geographic data via pages.

The user browser 418 connects to the web server 402 via the connection420. The user browser 418 logs into the web server 402 by entering alogin and a password. The web server 402 transmits a page to the userbrowser 418 so that the user browser may enter a search criteria andidentify a telecommunication network having network elements andgeographic elements that may be viewed, monitored, or configured. Theuser browser 418, or more particularly the user using the user browser,enters a search criteria, such as an intersection of streets or anaddress of a street.

The user browser 418 transmits the search criteria to the web server 402in a page. The web server 402 transmits the search criteria to the mapserver 410 in the form of a page containing data that, when executed,operates as a request for the map server 410 to obtain a geocodecorresponding to the search criteria.

The map server 410 receives and executes the page. The geocode generator412 generates a geocode that corresponds to the search criteria. In thisexample, the geocode is a latitude and longitude pair corresponding tothe address provided as the search criteria.

The map server 410 transmits the geocode to the web server 402 as aresponse in the form of a page. The web server 402 receives the pagefrom the map server 410, identifies the geocode data in the page,generates a new page having the geocode, and transmits the page to theuser browser 418.

The user browser 418 receives the page with the geocode, executes thepage, and transmits a new page to the web server 402 requesting a listof cells and other network elements in a search range of the geocode.The web server 402 transmits the request for the list of cells and othernetwork elements to the map server 410 in a form of a page.

The map generator 414 determines the list of cells and other networkelements within the search range of the specified geocode. The mapgenerator 412 communicates with the database server 404 to obtain theidentification of the cells and other network elements within the searchrange of the geocode. The database server 404 responds to the query fromthe map generator 414 with the identification of the cells and othernetwork elements within the search range of the geocode. The map server410 then transmits the identification of the cells and other networkelements to the web server in a page.

The web server transmits the identification of the cells and othernetwork elements to the user browser 418 in a page. The user browser 418receives the identification of the cells, executes the page, andtransmits a new page to the web server 402 requesting a map to displaythe network elements and the geographic elements in the search range.The web server 402 receives a communication from the user browser 418and transmits a page to the map server 410 requesting generation of themap.

The map generator 414 generates images and text of the network elements,including any associated performance elements, and the geographicelements for the map and transmits the map to the web server 402 in apage. The web server 402 includes the map received from the map server410 in a page that is transmitted to the user browser 418. The userbrowser 418 receives the page, and the map is displayed to a user. Themap may contain network and performance elements and geographic elementsdepicting a telecommunication network. For example, the map may displaythe network elements and the geographic elements of thetelecommunication system 202 depicted in FIG. 2.

In another example, the user browser 418 communicates with the webserver 402 using pages via the HTTP protocol. In this example, the userbrowser 418 has connected with the web server 402, and a map isdisplayed to the user browser. The map displays the telecommunicationsystem 202 of FIG. 2. In addition, the display displayed to the userbrowser 418 comprises a data entry and search tools panel for entry ofsearch criteria and search navigation and an output panel to displaynetwork data.

The user using the user browser 418 selects a network element, such asthe cell 208. Selecting the cell 208 initiates a communication from theuser browser 418 to the web server 402. Based on the communication fromthe user browser 418, the web server 402 will communicate with one orboth of the database server 404 and the map server 410. For example, theGMS 104B may be configured to generate a new map in which the selectedcell 208 is centered in the map. A zoom may be effected, therebygenerating a new map.

Selecting the cell 208 may require the web server 402 to obtain networkdata and geospatial data from the map server 410. Such network data andgeospatial data may include cell identification, trouble ticketidentification, graphical elements depicting status of a cell or atrouble ticket, including color or shape designations, and other networkdata, including status identification, such as dropped, blocked, closed,fast busy, or unspecified for trouble ticket type, and cell designationsfor cells.

The web server 402 also may require network data from the databaseserver 404. For example, the web server 402 may request network data forcells, cell sites, trouble tickets, and other network elements orparameters, such as cell site identification data, performancestatistics, and network event data.

In this example, when the user selects the cell 208 and transmits a pageto the web server 402 identifying the selected cell, the web server 402queries the database server 404 to obtain the network data associatedwith the cell 208. This network data includes cell site information,such as region, market, site identification, site description, latitude,longitude, on-air date, status, and/or antenna height. The network datamay be combined with static data, such as the names “region”, “market”,“site identification”, “site description”, “latitude”, “longitude”, “onair date”, “status”, and/or “antenna height”. The network data obtainedfrom the database server 404 is combined with the static data andtransmitted to the user browser 418 in the form of a page. If geospatialdata or network data is obtained from the map server 410, the web server402 will combine that network data and geospatial data with the networkdata obtained from the database server 404 and any static data to formthe page.

In another example, the user browser 418 is connected to the web server402. The user browser 418 communicates with the web server 402 usingpages. In this example, a map is generated to the user browser 418depicting the telecommunication network 202 of FIG. 2.

The user may select any network element for viewing, monitoring, orconfiguration. The user selects a trouble ticket 232. The selectioninitiates generating a page to the web server 402 identifying theselected trouble ticket 232.

The web server 402 queries the database server 404 to obtain the networkdata associated with the trouble ticket 232. The database server 404responds to the web server 402 with the network data associated with thetrouble ticket 234. Trouble ticket network data may include a troubleticket identification, a trouble type, an issue date, latitude of theproblem, longitude of the problem, one or more cross streets identifyingthe location of the problem, a city, a state, a zip code, a signalstrength for the call, and/or identification of the handset used by thecustomer.

The web server 402 combines the trouble ticket network data with thestatic data and geospatial data, if any, and generates a page. The webserver 402 transmits the page to the user browser 418.

In another example, the user browser 418 connects to the web server 402via the connection 420. In this example, the user browser 418communicates with the web server 402 using pages. After the user logsin, the web server 402 transmits a page to the user browser 418providing for the entry of a search criteria, such as an address or anintersection. In this example, the user enters an address as the searchcriteria and makes a selection to display a map having network elements,including any associated performance elements, and geospatial elementswithin a search range of that address.

The web server 402 receives the search criteria and transmits the searchcriteria to the map server 410. The map server 410 geocodes the searchcriteria and generates a map of the geocoded search criteria to the webserver 402. In this example, the map server 410 obtains a list of thenetwork elements within a search range of the specified address. The mapserver 410 transmits the identification and list of the network elementsto the web server 402. The web server 402 includes the identificationand list of the network elements and the map in the page transmitted tothe user browser 418. In this example, the generated map has displayelements that identify the network elements, performance elementsassociated with the network elements, and the geographic elements of thetelecommunication network of FIG. 5A. As a result, the display to theuser includes the map 502 identifying the telecommunication network ofFIG. 5A and an identification and listing of the network elementsdepicted in FIG. 5A, including the associated performance elements. Theuser can select the network elements and network data and navigate asdescribed above.

Multiple performance elements, including sectored performance elements,may be generated for a single network element. For example, a networkelement may be depicted by a circle on a map. The circular networkelement may have multiple concentric rings identifying multipleperformance elements. Each performance element may have a differentperformance characteristic signifying one or more performance levels forone or more attributes. In this embodiment, the center circle may beconfigured to depict a first performance characteristic for a firstperformance attribute, the first concentric ring may be configured todepict a second performance characteristic for a second performanceattribute, the second concentric ring may be configured to depict asecond performance characteristic for a third performance attribute, andthe third concentric ring may be configured to depict a thirdperformance characertistic for a fourth performance attribute.

For example, the center circle may be configured to depict one or moreperformance characteristics for percent blocks, the first concentricring may be configured to depict one or more performance characteristicsfor percent drops, the second concentric ring may be configured todepict one or more performance characteristics for erlangs, and thethird concentric ring may be configured to depict other performancecharacteristics for another performance attribute. Each circle and/orconcentric ring may be configured to display one or more performancecharacteristics, such as a different color, depending on a valueidentified for each performance level for a performance attribute. Avalue may be selected for performance metric limits for percent blocks,including a first color for normal, a second color for moderate, and athird color for excessive. The value for each of the normal, moderate,and excessive may be entered or otherwise designated. If the percent ofblocks matches or exceeds the value, then the color will change fromnormal to moderate or excessive, depending on the limit value selectedand the actual data value.

It will be appreciated that the performance element need not be acircle. Additionally, one or more performance elements may be generatedfor a single network element or one or more network elements. Forexample, a cell site may have three sectors, one for each of threeantennas. In this example, the performance elements may be parsed into athird of a circle or concentric ring so that a performance element isgenerated for each of the three sectors of the cell site. If more thanone performance element is to be used for a single network element or isto be used for associated components, equipment, or network elements ata single geographic location or area, such as described above, they arereferred to as “sector performance elements” herein. Other examplesexist. A sector may include a section or any portion. It need not be anequal portion.

A performance element for a communication network may depict performanceattributes other than call performance data. For example, an outerconcentric shape or portion of a concentric shape may identify acoverage area for a network element. In this example, an outerconcentric ring may depict the total coverage area of a cell site.

Moreover, the performance element may be a sectored performance elementdepicting a beam width of each cell sector. Thus, one sector of a cellsite may have a first range, and the second sector may have a secondrange.

In this example, the network element may have at least two sectoredperformance elements, the first depicting the first range, and thesecond depicting the second range. Therefore, the performance elementsfor the first sector and the second sector will be of different shapes,each depicting the coverage area of that sector over the geographic areaidentified by the map.

Also in this example, the cell site may not have an antenna for a thirdsector. Thus, performance elements may be depicted for the first andsecond sectors in this example. Alternately, a third sector may existand be depicted by a performance element that is less than a full third,i.e. 120°, of a circle and/or concentric ring. Additionally, a shapeother than a concentric ring may be used to depict the coverage areasince the coverage area may not fully exist in a ring configuration. Forexample, a polygon having an odd shape may depict the true coverage areaof a sector of a cell site.

It will be appreciated by these examples that multiple performanceelements having multiple performance characteristics, including sectoredperformance elements having sectored performance characteristics, may beused for a single network element depicting varied performanceattributes. The performance elements need not be concentric or of thesame shape. Nor do the performance elements need to be of a specificshape. The performance elements and the performance characteristics forthose performance elements may be configured as needed to depict theperformance attributes of any network. These performance elements andperformance characteristics include sectored performance elements withsectored performance characteristics, with each having non-uniformshapes or other characteristics.

It will be appreciated that, while examples of network elements,performance elements, and performance characteristics are given hereinwith respect to a communication network, the systems and methods hereinapply equally to other types of networks. For example, network elements,performance elements, and performance characteristics may be used foroil/gas networks, store networks, packaging and other business networks,or any other networks that may depict data geographically and/or withrespect to performance attributes.

FIG. 5B depicts an exemplary embodiment of a portion of the network map502A depicted in FIG. 5A. In this example, multiple sectored performanceelements are generated by the GMS 104B for a network element.

The map 502A depicts three cells 562-566, each having three sectors.Thus, the first cell 562 depicts three sectors 568-572. The second cell564 comprises three sectors 572-576. The third cell 566 also depictsthree sectors 580-584.

In the example of FIG. 5B, each of the performance attributes for theperformance elements of each of the sectors 568-572 of the first cell562 are the same. Additionally, the performance attributes of theperformance elements of the sectors 572-576 of the second cell 564 arethe same. Additionally, the performance attributes of the performanceelements of the sectors 580-584 of the third cell 566 are the same.Thus, each of the sectors 568-572 of the first cell 562, each of thesectors 572-576 of the second cell 564, and each of the sectors 580-584of the third cell 566 appear the same. However, each performance elementcan be configured separately for each sector of each cell.

The GMS 104B has a rubber band feature. The rubber band feature enablesa user to select an area on the map and to zoom into that select area.Any area may be selected by the user. Preferably, a rectangle may beused by a user to select a selectable area for the rubber band area.However, the GMS 104B may be configured to use any type of shape orconfiguration, including a circle, an oval, a square, a rectangle, apolygon, or some other type of designation to delineate the rubber bandarea. A rubber band area 586 is depicted in FIG. 5B by a dashedrectangle.

After the rubber band area 586 is selected, the user may zoom in to therubber band area 586. This action will generate a new map for thezoomed-in area.

FIG. 5C depicts an exemplary embodiment of an area that has beenselected as a rubber band area for which a zoom has been selected andfor which a map 502B has been re-generated for the zoomed area. In theexample of FIG. 5C, the performance characteristics for the variousperformance elements of each sector 568-572 of the first cell 562 havebeen altered. By way of example, the first sector 568 comprises a firstsectored performance element 588, a second sectored performance element590, a third sectored performance element 592, and a fourth sectoredperformance element 594. Similarly, the second sector 570 has a firstsectored performance element 596, a second sectored performance element598, a third sectored performance element 600, and a fourth sectoredperformance element 602. Likewise, the third sector 572 has a firstsectored performance element 604, a second sectored performance element606, a third sectored performance element 608, and a fourth sectoredperformance element 610.

The sectored performance elements 588-610 may be configured to depictany performance characteristics for any performance attribute for anyselected network element. Thus, depending on the type of networkinvolved and the type of network element involved, the performanceelements and the sectored performance elements may be different.

In one embodiment for the network map 502B of FIG. 5C, the firstsectored performance element 588, 596, and 604 of each sector 568-572depicts performance characteristics for percent of call blocks (theperformance attribute). The second sectored performance elements 590,598, and 606 of each sector 568-572 depicts performance characteristicsfor call drops. The third sectored performance elements 592, 600, and608 depict performance characteristics for erlangs. The outer sectoredperformance elements 594, 602, and 610 depict the coverage area of eachsector 568-572. It should be noted that the coverage areas depicted bythe fourth sectored performance elements 594, 602, and 610 are forexemplary purposes only and may be larger, smaller, and of differentshapes in another system or with different types of data.

It will be appreciated that the other cells 564 and 566 depicted in FIG.5C similarly may have sectored performance elements, each with the sameor different performance characteristics generated according to selectedperformance levels of selected performance attributes. For simplicity,these sectored performance elements and sectored performancecharacteristics are not depicted on FIG. 5C. Other examples and othertypes of sectored performance elements, associated performancecharacteristics, and associated selected performance levels ofperformance attributes may exist.

FIG. 6 illustrates an exemplary embodiment of an implementation ofcomponents of a GMS. The implementation of FIG. 6 illustrates one to Mweb servers, one to N database servers, and one to O map servers, whereM, N, and O represent any number greater than one. In the implementationof FIG. 6, the web server 402, the database server 404, and the mapserver 410 may communicate with each other via a link capable oftransmitting communications, such as a transmission controlprotocol/internet protocol (TCP/IP) link.

One or more instances of the logical components of a GMS may be locatedon a physical platform. For example, one or more instances of a webserver may be located on a computer platform. Such an example isdepicted in FIG. 7A. For simplicity, a database server is not depictedin FIG. 7A, but an instance of a database server would be present.

In addition, one or more instances of the logical components of a GMSmay be configured as a redundant system. For example, an instance of aweb server may connect to more than one instance of a map server inwhich a first instance of the map server is designated as a main and atleast another instance of the map server is designated as a redundantbackup. Although, it will be appreciated that an instance of a GMScomponent may be connected to more than one instance of anothercomponent without any of the instances being redundant systems.

An example of an implementation having an instance of a web server 702connected to two instances of a map server 704 and 706, in which oneinstance of a map server 704 is a main system and the other instance ofthe map server 706 is a redundant system, is depicted in FIG. 7B. Themap servers 704 and 706 reside on two platforms 708 and 710. FIG. 7Balso depicts an instance of a web server 712 that is connected to threeinstances of a map server 714-718, none of which are redundant systems.For simplicity, a database server is not depicted in FIG. 7B, but aninstance of a database server would be present.

In any of the examples of FIGS. 4-7, the map server can be configured toprovide communication load balancing. Each map server then determinewhether it can process additional communications and generate geocodesand maps. Each map server transmits a communication to the web serveridentifying its processing load and capabilities. The web server thendetermines which map server will process additional communications.

In addition, the map server can be implemented as two separatecomponents—namely, the geocode generator and the map generator. In thisconfiguration, the geocode generator will reside as an instancephysically separate from the map generator. This configuration canincrease processing efficiency if the map generator will require greaterprocessing to generate a map with images and text than the geocodegenerator generating the geocode.

FIG. 8 illustrates an exemplary embodiment of a graphical interface usedto enter, display, and navigate through network data and geospatial dataused in conjunction with the GMS. The graphical interface 802 of FIG. 8comprises display components for a geospatial and/or network data inputor output (GNDIO) 804, a search tools and data entry (STDE) 806, and anetwork data output (NDO) 808. In some configurations, the graphicalinterface 802 also may be configured with a legend 810, a zoom in/out812, and optional navigation tools 814. Different, fewer, or greaterdisplay components may be used.

The GNDIO 804 displays the map generated by the map generator 414. Thismap comprises network data and geospatial data. The map displays displayelements that represent geographic elements, network elements, andperformance elements within a search range of a geocode, such as aradius or a distance. Any designated search range may be used for adisplay, including different units of measurement. For example, thetelecommunication system 202 of FIG. 2 may be depicted in the GNDIO 804for a search range of 5.0 kilometers (km) around a specified geocode.

A user may select (i.e. “click on”) any of the network elementsdisplayed in the GNDIO 804, including trouble tickets, to display moredetailed information about the network element. The GNDIO 804 also maybe used to enter network data, such as configuration data. Forsimplicity, graphical representations of display elements, such asnetwork elements, are referred to as those display elements, such asnetwork elements.

The STDE 806 allows a user to enter search criteria. The STDE 806 maycomprise tabs for entry of search criteria to identify a geocode or anetwork element. For example, the STDE 806 may comprise tabs for entryof an address, a cell, a trouble ticket, a switch, a trading area, abase transceiver, or a network event.

The NDO 808 displays network data and geospatial data. The NDO 808 maycomprise tabs for output criteria. For example, the NDO 808 may comprisetabs to display network data for a cell, a trouble ticket, a switch, abase transceiver, an identification of cells in a search range, or anidentification of trouble tickets in a search range.

The legend 810 identifies components and colors or other identifyingdesignations displayed in the GNDIO 804 and provides a description ofthe components and of the identifying designations. For example, thelegend can identify cell sites and status, trouble areas, coverage, anddefinable trouble areas.

The zoom 812 allows a user to zoom in or out of a selected area of themap produced in the GNDIO 804. If a zoom in or out is selected, a newmap is generated.

The navigation tools 814 allow a user to navigate through other variousoptions and screens available from the GMS. This includes other displaysand other functions.

FIGS. 9-35 illustrate exemplary embodiments of a graphical interface.However, other graphical interfaces or components of graphicalinterfaces may be used.

A browser is used to navigate through screens of the graphicalinterface. Since the graphical interface is useable in conjunction withthe browser, multiple users can access the GMS via an IP connectionusing pages. This allows a user to quickly and easily navigate throughthe screens of the graphical display, view and monitor network data andgeospatial data for network elements, and enter configuration data andother network data for the network elements. Any browser may be used.

FIG. 9 depicts an example of a screen in which a search criteria may beentered. The screen 902 has a GNDIO panel 904, an STDE panel 906, an NDOpanel 908, and navigation tools 910. The STDE panel 906 and the NDOpanel 908 have navigation tabs 912 and 914 for selecting options forsearch and entry of data and for data output, respectively.

The user can select navigation tabs in the STDE panel 906 to enter asearch criteria including an address, a trouble ticket, a major tradingarea (MTA), a base transceiver station (BTS), or a cell site. In exampleof FIG. 9, a user may search with any component of an address, includinga street address, an intersection, a city, a state, or a zip code or anycombination thereof. Once a user has entered the search criteria, theuser may select the “Display Map” to initiate the search.

FIG. 10 depicts an example of a screen displayed to a user after asearch has been initiated. In this example, the user entered a streetaddress, a city, and a state. The GMS receives the search criteria,determines the network data and geospatial data corresponding to thesearch criteria, and transmits the network data and the geospatial datato the user. A map is generated to the user in the GNDIO panel 904. Themap displays the network elements and the geographic elements within asearch range of the search criteria. The search range can bepredetermined or set on a user-by-user basis.

In the example of FIG. 10, the map centers at the geocode of the addressentered as the search criteria. The map identifies cells, such as thecell 1002, trouble tickets, such as the trouble ticket 1004, knowntrouble areas, such as the known trouble area 1006 (i.e. a user orengineer defined trouble area), a customer defined trouble area (CDTA)1008 streets, such as the street 1010, and streams, such as the stream1012.

A zoom 1014 and a legend 1016 also are displayed to the user. The zoom1014 allows a user to zoom into, or zoom out of, the map area displayedto the user. The legend has legend components that identify networkelements and geographic elements. In the example of FIG. 10, the networkelements can be color-coded so that a user may know a status of thenetwork elements quickly by viewing their color. In addition, any of theareas of the map displayed to the user can be color-coded so that a usermay quickly identify the status of the network coverage of the area. Inaddition, other network data can be displayed and color-coded. Forexample, the trouble tickets can be color-coded so the status or aproblem associated with a trouble ticket is quickly known.

The legend displayed to the user can vary based upon a user profile andlayers selected for each user (See FIG. 28.) Layers may include CDTA,engineering defined trouble areas (also referred to as user definedtrouble areas or known trouble areas), engineering designed coverage,future cell sites, lakes and rivers, MTAs, marketing defined coverage,network events, parks and recreational areas, trouble tickets, and otherlayers. For example, if the trouble ticket layer is not enabled, theidentification and color-coding of trouble tickets will not be displayedin the legend. Moreover, the trouble tickets will not be displayed onthe map or in the NDO.

In the example of FIG. 10, the legend 1016 comprises legend componentsfor network cell status for on air, outage within seventy-two hours,current outage, and future site, coverage for excellent, very good,good, average, and poor, known trouble areas, customer defined troubleareas, and trouble tickets for blocked, dropped, fast busy, unspecified,and closed. Any number or units of time or units for coverage may beused, such as twenty four hours or degrees of coverage. Different,greater, or fewer legend components may be displayed.

When the map is generated to the user, network data for the networkelements is populated. For example, network data for cells and fortrouble tickets is populated when a map is generated. The system can beconfigured to default on selected navigation tabs based on a userselection.

In the example of FIG. 10, a list of cells with a color-coded cellstatus in a search range of 5.0 km or 0.045 degrees is displayed to theuser in the cells tab of the NDO panel. In addition, the latitude andlongitude of the address entered as the search criteria, the cells, thecell identifiers, and the color-coded status of each cell are displayed.It will be appreciated that other search ranges may be used.

FIG. 11 depicts an example of the tickets tab of the NDO. The ticketstab displays the range of 5.0 km (0.045 degrees) radius. In addition,the latitude and longitude correspondent to the search criteria isdisplayed. The ticket tab displays the network data associated with thetrouble tickets within the range. The trouble tickets are listed alongwith the ticket identifier, a color-coded ticket status, and the problemtype, such as dropped, fast busy, blocked, closed, or unspecified. Auser may select a check box to close the ticket if the ticket is notalready closed.

FIG. 12 depicts an example of site information displayed to a user. Auser can view the site information for any cell site by clicking on thecell site displayed in the map. This causes the GMS to transmit thenetwork data to the user for viewing. For example, the site informationmay comprise a region, a market, a site identification (ID), a sitedescription (Desc), a latitude of the cell site, a longitude of the cellsite, an on air date of the cell site, a cell site status, and/or anantenna height. The site information is populated with the network datawhen the user selects the cell site from the map.

FIG. 13 depicts an example of trouble ticket data displayed to a user. Auser can view trouble ticket data for a particular trouble ticket byclicking on the trouble ticket in the map. This initiates an action topopulate the network data for the selected trouble ticket. The troubleticket data may include a ticket identification (ID), a problem typeissue date, a latitude of the trouble ticket, a longitude of the troubleticket, one or more cross streets, a city, a state, a zip code, a signalstrength of the call, and/or an identification of the phone used by acustomer.

FIG. 14 depicts an example of network data displayed to a user fornetwork's statistics. A user may view the network statistics of anetwork element by clicking on the network element on the map. Asexplained above, this action initiates population of network data forthe site information tab. The GMS can be configured to initially displayinformation in the site information tab or in the network informationtab. The user then may switch between the two tabs. In the example ofFIG. 14, network statistics for a selected cell are displayed. Thenetwork data displayed in the network statistics tab may comprise theidentification of the switch associated with the cell site,identification of the cell site, and network statistics for the selectedcell site, including the date of a network event, attempts, drops,blocks, percent drops, percent blocks, channel erlang (cE), and busyhour (BH) for a call. A user may view reports of network statistics bymaking a selection from the available reports select box.

FIG. 15 depicts an example of a report that can be displayed to a useridentifying network statistics. In the example of FIG. 15, a reportgraphically identifies call attempts versus call drops and call blocks.Other reports are available to illustrate any of the network statistics.

FIG. 16 depicts an example of a screen in which the legend may beremoved from the screen. A user may toggle between displaying the legendand not displaying the legend. If the legend is not displayed, a selectbutton will be displayed in its place. A user may select the displaylegend button to view the legend on the screen.

FIG. 17 depicts an example of event/alarm data displayed to a user. TheGMS can be configured to display network statistic data or event/alarmdata on the network tab. For example, if the layer for the networkevents is enabled (see FIG. 28), then the event/alarm data will bedisplayed on the network tab. If the network events layer is notenabled, then the network statistics data will be displayed on thenetwork tab. Other configurations may be used. Also, an additional tabmay be added to the NDO for simultaneously viewing the event/alarm dataand the network statistics data. Alternately, the network statisticsdata and the event/alarm data may be viewed simultaneously in thenetwork tab.

In the example of FIG. 17, event/alarm data is displayed. Theevent/alarm data may comprise any network data to display events,alarms, or network statistics. The event/alarm data of FIG. 17 comprisesthe cell site identification (ID), the start of the event or alarm, theend of the event or alarm, the status of the cell site, and adescription of the event or alarm.

FIG. 18 depicts an example of a trouble ticket entered as a searchcriteria. The trouble ticket may be entered or a trouble ticket may beselected from the select box. After the user has entered the troubleticket data, the user may display a map showing network elements andgeographic elements within a range of the trouble ticket searchcriteria. The user initiates this action by selecting the Show Mapbutton. A map is generated in which the trouble ticket is centered inthe map area. In addition, the NDO defaults to a display for the ticketstab, as described above.

FIG. 19 depicts an example of a search criteria for an MTA search. Theuser can enter an MTA or select an MTA from the select box. The userinitiates the search by selecting a Display Market Map button. A mapidentifying the network elements within the selected MTA is generated.In addition, the GMS can be configured to default to display the ticketstab in the NDO. The tickets tab shall display the appropriate searchrange for the map. In this example, a search range of 236.5 km (2.128°)radius is displayed.

FIG. 20 depicts an example of a search criteria using a cell sitesearch. In this example, the cell site search may comprise initiallysearching by an MTA and then searching by a list of cells. A user firstcan enter an MTA. A list of cells is displayed in the STDE by selectingthe Show Cells button. A user can select one of the cells from the list,and a map is generated in which the selected cell is displayed in thecenter of the map. The map displays all network elements and geographicelements within a search range. In this example, the NDO is configuredto default to the Tickets tab. However, the NDO can be configured todefault to another tab, such as the Site Info tab or the Cells tab. Inaddition, the STDE can be configured for a different type of entry.

FIG. 21 depicts an example of a screen used to enter the cell site onlyas a search criteria. The user can enter a cell site or select a cellfrom the select box. A map is generated in which the map center is theselected cell site.

FIGS. 22A, 22B, and 23 depict examples of providing BTS events as asearch criteria. A map is generated in which the map center is theselected cell site with the BTS event. Network statistics are generatedfor the selected cell site in FIG. 23.

FIGS. 22A, 22B, and 23 also depict screens used to enter an MTA as asearch criteria. In FIG. 22A, a user can select an MTA from a select boxof a network statistic search for a BTS event search. Once the MTA isselected, a list of cells is displayed to the user in the STDE panel, asdepicted in FIG. 22B. A cell can be selected from the STDE panel orselected from the map. When a cell is selected, as from the map, thesystem defaults to display the network statistics for the BTS statisticstab in the MDO.

FIG. 24 depicts an example of a screen used to enter a zip code for asearch criteria. A map is generated in which the map center is thecenter of the zip code search criteria.

FIGS. 25 and 26 depict an example of defining a trouble area. A useruses trouble area definition tools to define the trouble area. Multipletypes of definition tools may be displayed. In the examples of FIGS. 25and 26, selectable buttons for the definition tools are located in theupper portion of the map area and include a tool for defining a polygonof the area, a tool for defining a circular area, a tool for defining asquare area, and a button to save the defined area. The definition toolsalso include a button to exit the design mode.

The design mode exit button of FIGS. 25 and 26 resembles a hand. Thedesign mode exit button can be selected at any time during the troublearea definition process. If the design mode exit button is selectedwhile the user is defining a trouble area, the trouble area will not besaved. If a user exits the design mode, a button will be displayed that,when selected, allows a user to enter the design mode. See, for example,FIG. 24.

FIG. 27 depicts an example of a screen displayed to a user when the savebutton is selected during the design mode. This screen allows a user toenter a title for the trouble area, an anticipated date of resolution(DOR) for the problem or problems resulting in the trouble area, and acomment section for the proposed resolution. An identification, such asa number, is assigned to the trouble area. It will be appreciated thatdifferent, greater, or fewer data may be entered, and a different screenmay be displayed to a user for data entry. Also, a GMS may be configuredthat will not display the trouble area definition screen, but merelysave the trouble area once created. Moreover, other definition tools maybe used.

FIG. 28 depicts an example of a trouble ticket entry utility. A user mayenter identifying information for the trouble ticket, including thelocation of the call or caller and the problem experienced by thecaller. The identifying information may include a cross-street or streetaddress for the location of the caller experiencing the problem, a city,a state, a zip code, or a ticket problem type, such as dropped, blocked,fast busy, or unspecified. Other indicia may be included, such as acustomer name, a customer email address, a customer text pager number,or a customer phone number. A ticket identification (ID) can bedesignated by the GMS or entered by a user. Once the ticket identifyinginformation is entered, a user can initiate geocoding the ticket andassociating known network data to the ticket, such as a neighboring cellsite, by selecting a save button, such as the Geocode Ticket button. Theinformation may be saved by committing the ticket.

FIG. 29 depicts an example of a screen used to close multiple troubletickets. In this example, a user selects a check box for each troubleticket to be closed and selects the Close Tickets button to initiate theaction. This action causes an entry box to be displayed in which a usercan enter a resolution or reason for closing the ticket. The user alsocan choose to notify a client (i.e. the customer) sending an e-mail, amessage to a text pager, an automated voice response message, a voicemail, or another type of message identifying the resolution. The usercan finalize the ticket closing by selecting the Commit Ticket Closebutton.

FIG. 30 depicts an example of a menu that can be displayed to a user.Examples of some menu options include user profile to define the profileand options a user may have, layer options to select and define layeroptions for a user, labeling options to select and define labelingoptions for a user, map size, design control options, help options, andlogout. Different, greater, or fewer menu options may be used.

FIG. 31 depicts an example of layer options that are available forusers. Layer options may be enabled or disabled for individual users.For example, an engineer may have different selected layer options thana customer service person. Examples of layer options include customerdefined trouble areas, engineering defined trouble areas, engineeringdesigned coverage, future cell sites, lakes and rivers, MTAs, marketingdefined coverage, network events or network statistics, parks andrecreational areas, and trouble tickets.

FIG. 32 depicts an example of a screen used to define a user profile. Inthis example, a user may select options for a user classification, suchas an engineer or a customer service person, a default for a searchrange around a search criteria for which a map will be generated and forwhich network elements and geographic elements will be identified, andan option to display the legend on the screen display, to not displaythe legend, or to display the Display Legend select button. Different,greater, or fewer user profile options may be used.

FIG. 33 depicts an example of design control options. In this example, auser can be provided the ability to define trouble areas.

FIG. 34 depicts an example of options for selecting a map size displayedto a user. A user can select one of the buttons to control the size ofthe map displayed.

FIG. 35 depicts an example of a login screen. The login screen requiresa user to enter a valid login and a valid password for entry into theGMS. This provides a security measure so that only authorized personnelmay use the system.

FIG. 36 depicts an example of a screen used for configuration of aperformance layer. The screen is used to configure whether or not aperformance element is displayed, for which network elements thecorresponding performance element is displayed, which performanceattributes will be used to determine if a performance element will bedisplayed and, if so, the performance characteristic of the performanceelement, and the performance levels that are defined for eachperformance characteristic. In this example, two performance levels areconfigured for each of the performance attributes. These include awarning level and a critical level. For example, a performancecharacteristic signifying a warning level will be displayed for aperformance element if the number of dropped calls is greater than orequal to 100. Likewise, a performance characteristic signifying acritical level will be displayed for a performance element if the numberof dropped calls is greater than or equal to 500.

In addition, the performance characteristics can be configured using alogical operator, such as “and” or “or”. If the “and” logical operatoris used, all selected performance attributes must reach at least theconfigured performance levels before the performance characteristics ofthe respective performance elements will be displayed. In this example,a performance characteristic signifying a warning level will bedisplayed for a performance element if the number of blocks is greaterthan or equal to 5%. In this example, only one performance attribute wasselected. However, if other performance attributes are selected, such asblocks, percent drops, and percent blocks, then a performancecharacteristic signifying a warning level will be displayed for aperformance element if the number of blocks is greater than or equal to10, the percentage of drops is greater than or equal to 2, and thepercentage of blocks is greater than or equal to 5.

In addition, the logical operator “or” can be used in the example ofFIG. 36. When the “or” logical operator is used, the performance levelof only one of the selected performance attributes need be met beforethe performance characteristic signifying the performance level isdisplayed for the performance element. For example, if the performanceattributes of drops and blocks is enabled, then a performancecharacteristic signifying a warning level will be displayed for aperformance element if either the number of drops is greater than orequal to 100 or the number of blocks is greater than or equal to 10.

FIG. 37 depicts an example of a screen having multiple display elements,including geographic elements, network elements having eventcharacteristics, and performance elements having performancecharacteristics. In this example, cell sites are displayed as circles.Each of the circles are color coded (i.e. shaded in FIG. 37) with anevent characteristic to signify an event level. For this configuration,red would indicate a current event, such as a failure or a degradation,yellow would indicate an event occurred within a prior configured amountof time, such as 72 hours, and green would represent a healthy networkelement that has no current or recent events. In this example of FIG.37, different shades of gray are used in place of colors. Thus, thedarkest gray is used in place of green, a lighter gray is used in placeof red, and the lightest gray is used in place of yellow.

Each of the cells has a performance element with a performancecharacteristic that indicates a performance level. In this example, theperformance elements for the cells are concentric circles located aroundeach cell. The performance characteristic is configured as a color codeto signify a performance level of one or more performance attributes. Inthis configuration, green would indicate no significant performancelevels for a statistical attribute, yellow would signify a warning levelfor one or more performance attributes, and red would signify a criticallevel for one or more performance attributes. In this example of FIG.37, different shades of gray are used in place of colors. Thus, thedarkest gray is used in place of green, a lighter gray is used in placeof red, and the lightest gray is used in place of yellow.

FIGS. 38 and 39 depict examples of levels of coverage for a servicearea. FIG. 38 depicts a multitude of cell sites and trouble tickets inthe context of geographic elements, such as lakes and streams. Some ofthe cell sites have concentric circles as performance elements tosignify the performance level of those cell sites. In this example, thecell sites and the performance elements are shaded to signify theircorresponding event levels and performance levels. In addition, acoverage area is shaded on the display. In this example, a customerwithin the shaded area is within an area of service. A customer outsideof the shaded area, i.e. the white area, is not within an area ofservice. The map area displays all network elements, performanceelements, and geographic elements within a search range, such as 60.0km. In the example of FIG. 39, a smaller search range of 17.0 km isspecified. This smaller search area allows a user to view more detail ofnetwork elements, performance elements, and geographic elementssurrounding an identified network element.

FIGS. 38 and 39 also illustrate additional examples of a legend, anSTDE, an NDO, and navigation tools. The legend of FIGS. 38 and 39 allowsa user to select a distance of a search range surrounding a selectednetwork element for which a map will be generated. This example depictssearch ranges in kilometers, including the ability to zoom in and tozoom out in selected ranges. However, other units of measurement may beused, such as radius, miles, ordinates, other metric units, and othernon-metric units. In addition, different tabs are illustrated in theSTDE and the MDO. Also, different tabs are identified for the navigationtools, and different icons or buttons are used for the design mode andthe associated help for the design mode.

The GMS 104 may be configured with a time series viewer, a graph viewer,and/or a report viewer. The GMS 104 enables visualization of datahistorically by providing the ability to view maps of data as it wasminutes, hours, days, weeks, months, years, or some other configurableperiod of time in the past. A point in time may be selected as well asthe duration of time for depiction of the data. The time and durationassociated with the data to be generated may be user defined.

The time series viewer generates data over a selectable period of time.The time series viewer generates time sequenced maps that depict achange in data over a series of time. The starting time and duration isselectable by a varying time granularity, including daily, weekly,monthly, yearly, or some other value for the time granularity.

The time series viewer may be used to analyze pockets of data as theyoccur over time, such as by identifying a pocket of cell trafficcongestion as that congestion occurs over time. The time series viewerenables visualization of data geographically by adding a time dimensionto the spatial and geographic dimensions. A user may selectively advanceforward or reverse by a selectable value of time, including a minute,hour, day, week, month, year, or some other time granularity.

Preferably, the time series viewer generates for display a series ofmaps, similar to the way a media player generates data for viewing ofstreaming video. Preferably, each map in the series represents anillustration of performance elements having performance characteristicsfor performance attributes in a geographic region at a moment in time.

FIGS. 40-45B depict an exemplary embodiment of the data viewer. The dataviewer 4002 of FIGS. 40-45 includes a map viewer, a visualizationssetting map, a graph viewer, and a time series viewer. It will beappreciated that another data viewer may include one or more of thepreviously listed items. Thus, a data viewer may include only a timeseries viewer, only a map viewer, only a graph viewer, or anycombination thereof.

FIG. 40 depicts an exemplary embodiment of a map viewer of a dataviewer. The screen depicts sectored performance layers for multiplesectors for multiple cells. Each sectored performance element for eachsector of each cell may be independently identified and may show adifferent performance characteristic, depending on its performance leveland performance attribute.

The data viewer 4002 of FIG. 40 includes a map viewer 4004. The mapviewer 4004 enables a user to view network elements in geographicrelation to each other and to geographic elements. The network elementsmay include performance elements having performance characteristics,including sectored performance elements having sectored performancecharacteristics. The map viewer 4004 of FIG. 40 enables the user toselect one or more network elements to generate feature data in a sideframe 4006 on a portion of the generated screen. In an example of FIG.40, a trouble ticket identified as trouble ticket 2532 was selected,thereby generating the detailed attributes of that trouble ticket fordisplay in a side frame 4006. Similarly, any cell or other networkelement may be selected to display the detailed attributes for thatnetwork element.

The data viewer 4002 may include multiple tabs and/or menu selections tosearch or view data or to implement one of the components of the dataviewer. For example, the data viewer 4002 may have a map viewer 4004, aside frame 4006, a data viewer selector tabs 4008, and a menu selector4110.

The map viewer 4004 generates a map of a selected geographic region andnetwork elements. The map viewer 4004 may zoom in or out a selectablelevel.

The side frame 4006 may depict a search area for entry of an address, anMTA, a BTA, or some other search area by selecting the search tab 4012.Further, the side frame 4006 may depict detailed attribute feature dataof a selected network element by selecting the feature data tab 4012.The side frame 4006 further may be used to select and generate reportsusing the reports tab 4016.

The selector tabs 4008 may be used to generate a map of a search area,including geographic elements, network elements, and performanceelements. The menu selector 4010 may include one or multiple buttons forfunction selections.

The search tab 4012 enables a user to enter criteria to generate a mapor feature data. For example, the search tab 4012 may enable a user tosearch by an address, an MTA, or a BTA. Other search criteria may beused.

The feature data tab 4014, when selected, is loaded with feature datainformation when a map feature, such as a cell site, cell sector, ortrouble ticket, is selected. If a network element is selected, thefeature data tab 4014 is loaded with the network elements feature dataand thumbnail performance graphs.

The reports tab 4016 enables a user to use the report tool. Uponselection of the reports tab 4016, a user may specify input foravailable reports.

The map tab 4018 enables a user to generate a map of a selected area.The map may include geographic elements, network elements, andperformance elements.

The results tab 4020 generates detailed graphs and reports when thedetailed graphs and reports are available. When the results tab 4020 isnot being used to display a detailed report or a graph, it is empty.

The visualization settings tab 4022 enables a user to apply performancefilters and rendering customizations. Performance filters are used toidentify map features, such as a cell or a cell sector or anothernetwork element, that meet or exceed a filter threshold. The generatedmap thereby is reduced to include the network elements that pass thefilter's constraints. Rendering customizations allow a user to customizehow a performance element or performance characteristic is rendered on amap.

The administrative tab 4024 appears if a user has administrativeprivileges. The administrative tab 4024 enables a user to accessexisting administrative pages, such as a user management and a groupmanagement. A user management page enables an administrator to add orremove users and change a user's information. The group management pageenables an administrator to add or remove user groups and to add orremove users to and from user groups.

The selector tabs 4008 may be used to generate a map of a search area,including geographic elements, network elements, and performanceelements, by selecting the map tab 4018. A results tab 4020 may be usedto display performance graphs and to select attributes to generate forperformance graphs. A visualization settings tab 4022 may be used toselect and set performance metrics of performance characteristics forperformance elements. An administration tab 4024 may be used to generateuser group and user management data. Other tabs may be included, andsome of the tabs depicted in this embodiment may be excluded.

The menu selector 4010 may include one or multiple buttons for functionselections. In the embodiment of FIG. 40, the menu selector 4010includes a legend toggle 4026 to toggle the display of a map legendbetween visible and hidden. A layer selector button 4028 enables displayof a layer selection pop-up dialog page that allows a user to selectwhich performance layers shall be visible. A unit selector button 4030enables selection of a unit of measure used for the map, such as miles,kilometers, meters, feet, or another unit of measure. A distancemeasurement button 4032 enables measurement of distance from one pointto another. The unit measurement button 4033 is used by marking a pointon the map and then moving to another point. The approximate distancebetween the two points is displayed in a status bar below the map.

A refresh button 4034 refreshes the map display. An identify mode button4036 turns the identify mode on and off. A center button 4038 causes themap to be re-centered at a selected click point on the map when thecenter mode is engaged. A pan mode button 4040 enables the map to bepanned by dragging the map in any direction. A zoom in button 4042enables the map to be centered and zoomed-in at the same time whileengaged. The zoom out button 4044 enables the map to be centered andzoomed-out at the same time while engaged. A feature creation tool 4046will enable a user to create new features by drawing them on the map.The feature creation tool 4046 will allow creation of ellipses,rectangles, polygons, and other features. The time series viewer button4048 enables generation of a time series view of the current map area.

The map viewer 4004 depicts cells having multiple sectored performanceelements. For example, a first cell 4050 includes three sectors4052-4056. Each sector 4052-4056 has four sectored performance elements.The center sector performance element, depicted by a circle having threesectors, depicts a first performance attribute characterized by a firstperformance characteristic. A second sectored performance element,depicted by a first concentric ring, depicts a second performanceattribute characterized by a second sectored performance characteristic.A third sectored performance element, depicted by a second concentricring, depicts a third performance attribute depicted by a third sectoredperformance characteristic. Additionally, a fourth sectored performanceelement, depicted by a third concentric ring, depicts a fourthperformance attribute characterized by a fourth sectored performancecharacteristic.

In the example of FIG. 40, the sectored performance characteristics forthe sectored performance elements are generated based upon selectedperformance levels for each sectored performance element. Thus, forexample, the sectored performance element for the center circle maydepict varying colors based upon normal, moderate, and excessive levelsentered for a percent block and the corresponding color swatch for eachsectored performance characteristic. The first concentric ring maygenerate varied colors depending on values entered for levels of apercent drop and the corresponding color swatch for each sectoredperformance characteristic. The second concentric ring may depict variedcolors depending on values entered for levels of erlangs and thecorresponding color swatch for each sectored performance characteristic.

The outer ring for the cell 4050 may depict a coverage area and may havea constant color for the sectored performance characteristic. However,the shape and dimensions of the outer concentric ring may vary dependingon the actual value of the coverage area for that cell sector 4052-4056.Thus, the outer concentric ring may be greater for the first sector 4052than for the third sector 4056, because the coverage areas for thesectors 4052 and 4056 may be different. Thus, the dimensions of thesectored performance elements may be different.

The map viewer 4004 generates data identifying other cells 4058-4068 fora selected geographic area. Each of the cells 4058-4068 have sectoredperformance elements for which sectored performance characteristics aregenerated, depending on identified performance levels of performanceattributes for each sectored performance characteristic.

The cell 4062 similarly has three sectors 4070-4074. However, the firstsector 4070 and the second sector 4072 do not overlap in this instance.In this example, the sectors 4070-4074 depict the actual beam width ofeach antenna for each sector. Thus, a gap in coverage for the beamwidths of the antennas for the first and second sectors 4070 and 4072exists.

Additionally, the cell 4068 only displays the performance layeridentifying the coverage for the cell. Thus, performance layers may beselected and deselected based upon varying views and cell locations. Inthis instance, the performance layers for percent block, percent drop,and percent erlangs have been deselected and are not depicted. However,based upon the data, the performance layers may be added to one or morecells.

FIG. 41 depicts another example of a screen used for configuration ofone or more performance layers. The configuration screen of FIG. 41 isused to configure whether or not one or more performance elements,including sectored performance elements, are displayed, for whichnetwork elements corresponding performance elements are displayed, whichperformance levels of which performance attributes will determine if aperformance element will be displayed and, if so, the performancecharacteristic of the performance element, and the performance levelsthat are defined for each performance characteristic. In this example,search filters and performance metric limits are used to identifyperformance levels for performance attributes and associated performancecharacteristics. A search area may be selected for selected address, amarket trading area (MTA), or a basic trading area (BTA).

The visualization settings selector 4104 enables the user to selectmultiple performance levels (i.e. performance metric limits or limitvalues for a filter) and associate a performance characteristic (i.e. acolor from the color swatch) to be generated for a performance elementbased upon data attributes that may occur for the selected performancelevels.

Additionally, a user may select whether the performance elements havingperformance characteristics are displayed for a cell site or whethersectored performance elements having sectored performancecharacteristics are displayed for cell sectors. In the example of FIG.41, cell sectors are selected. Therefore, sectored performance elementshaving sectored performance characteristics will be displayed. Theselectable options that enable a user to select whether metrics will begenerated for a cell site or a cell sector are referred to as radiobuttons.

Additionally, a user may identify a starting and ending date.Alternately, other configurations may include a start and end dateand/or other selected time unit. A user may identify a time granularity,such as an hour, day, week, or other granularity.

In this example, performance metric limits are identified for percentblocks, percent drops, and erlangs. Each performance metric identifies amoderate and excessive level with a corresponding color to be generatedas the performance characteristic if that performance level (i.e.performance metric limit) is met. If the performance level does not riseto the level identified for the moderate or excessive level, a defaultcolor will be generated for the performance characteristic for a normallevel for each of the percent blocks, percent drops, and erlangs.

In other examples, a user may specify a limit value for a search filtermetric. In the example of FIG. 41, a user may have identified a valuefor percent blocking, percent drops, percent handoff blocks, percenthandoff drops, percent minutes utilization, percent max channelutilization, erlangs, and max channels busy. If the actual value of thedata is greater than or equal to the limit value specified by the user,the corresponding color specified for that filter type will be generatedas the performance characteristic of the performance element. It will beappreciated that other performance characteristics may be identified.For example, shades of gray, white, and black may be used to identifyvarious performance levels. Alternately, other performancecharacteristics may be used, including cross-hatching, other fill types,and different shape configurations.

Search filters enable a user to select the type of visualizationsettings for the performance elements or sectored performance elementsthat will be generated having performance characteristics or sectoredperformance characteristics. With the search filters, a user may selectthe performance metric limits (i.e. performance levels) for theperformance characteristics or sectored performance characteristics thatwill be generated for performance elements or sectored performanceelements.

The limit value for the filter type typically is used when depicting ahigh level view of an MTA or a BTA. In the example of FIG. 20, a valueof 0.21 is specified for the percent blocking and the correspondingcolor selected is white. Therefore, for cell sites having a percentblocking greater than or equal to 0.21, the performance characteristicswill be generated as a white circle. Generally, the limit value for thesearch filters is used for a large geographic area. The performancemetric limits for the search filters often is used for cell sectors orcell sites at a smaller geographic area for which a zoom and/or rubberband zoom may be selected.

Not only can the user select the starting and ending dates under thevisualization settings, the user also may select the icon located to theright of the start date and the end date to generate a pop-up calendarused to select a date. The pop-up calendar enables a user to easilyselect a day, a month, and a year by selecting from a pull-down list orfrom a date shown for a calendar.

Colors may be selected for the color swatches to the left of the normal,moderate, and excessive values. The colors selected for the colorswatches then will be generated as the performance characteristic forthe performance elements on the map in this example.

FIG. 42 depicts an exemplary embodiment of a map viewer with cellattribute details and cell attribute graphs in the side frame 4006. Theattribute data can be displayed in the feature data tab 4014 afterclicking on a cell site.

FIG. 43 depicts an exemplary embodiment of a graph viewer. The graphviewer 4302 enables a user to graph attribute and attribute relateddata. The graph viewer 4302 may be used to select a set of featureattributes to be included on one or more graphs, to change a graph type,such as from line, bar, pie, etc., to increase or decrease the amount oftime represented on the graph, and to change the time period representedon the graph. The graph viewer 4302 may be enabled by selecting at leastone graph from the side frame 4006 or from selecting the results tab4020.

The graph viewer enables a user to display individualized data for aspecific sectored performance element, such as a specific sector on acell. Alternately, the graph viewer 4302 may enable a user to selectdata for display for a whole performance element, such as a cell.Selecting a performance element or a sectored performance element causesthe data attributes to be depicted in the side frame 4006 along with oneor more graphs of the attribute data, specific to the performanceelement or the sectored performance element that was selected.

Selecting at least one graph depicted in the side frame 4006 causes thegraph analysis tools for the graph viewer 4302 to be generated to thescreen. Alternately, the results tab 4020 may be selected to generatethe graph analysis tools to the main frame.

One or more data sets may be added to the graph. For example, percentblocks and percent drops may be located on one graph, such as in theexample of FIG. 43. However, a single data set may be generated to themain frame for the detailed graph.

When more than one data set is generated to the detailed graph 4306, thescale on the vertical column automatically is adjusted to identify theappropriate scales for the range of data for the data sets.

The time frame represented by the horizontal axis may be adjusted togenerate a time granularity for the detailed graph. A user may manuallyenter a starting (from) time, date, or other unit. Additionally, anending (to) time, date, or other unit may be entered. Alternately, auser may select a time, date, or other granularity from the pop-upcalendars that are generated from selecting the calendar icon to theright of the “from” and “to” fields. Further, the data granularity maybe selected from a pull-down menu, including hourly, daily, weekly,monthly, yearly, or some other unit of granularity.

The selected unit of data granularity will cause the detailed graph 4306to be generated starting with the “from” time or date, ending with the“to” time or date, and being generated in units identified by the datagranularity. In the example of FIG. 43, the detailed graph 4306 is shownat starting on the fourth day of the month, ending on the twenty-eighthday of the month, and showing data in units of time per day.

Additionally, a graph type may be selected. The graph type may include aline graph, a bar graph, a three-dimensional bar graph, and other typesof graphs.

A user may slide the detailed graph 4306 to the left or to the right byclicking and dragging the graph to the left or right. This moves thedetailed graph backward or forward in time and enables a user to quicklyanalyze the data points that are before or after the displayed datapoints. Alternately, a user can select the less time icon 4320 or themore time icon 4322 located on the upper and lower right portions of thedetailed graph 4306. Each time one of the two icons 4320 or 4322 isselected, a single time unit is removed or added to the detailed graph4306. In the example of FIG. 43, the data granularity 4316 is selectedas daily. Thus, if the less time icon 4320 or the more time icon 4322 isselected, the detailed graph will be decreased or increased by agranularity unit of one day.

FIG. 44 depicts an exemplary embodiment of a report tool. The reporttool 4402 provides detailed performance and attribute data for a networkelement, including a sectored performance element. The report tool 4402may be accessed by selecting the reports tab 4016.

A report may be generated by first selecting the type of report from thereport type tab 4404. The report type may include a top ten summary, asector summary, or some other report type. The geographic area then maybe selected from the market type selector 4406. For example, a user mayselect a city as the market type selector 4406. The granularity list4408 includes a variety of time intervals, including daily, weekly,monthly, yearly, and other units of granularity. The date may beselected from the starting date range 4410 and the ending date range4412. The date range may be entered manually or selected from the pop-upcalendar by selecting the calendar icon 4414. Additionally, the reporttool 4402 may be configured to automatically generate the ending dateonce the unit of granularity is selected from the granularity selector4408. When the generate button 4416 is selected, the report will begenerated in the report viewer 4418. Horizontal and vertical slider barsmay be used to view data if the data is greater than the window of thereport viewer 4418.

FIG. 45A and FIG. 45B depict an exemplary embodiment of a time seriesviewer. The time series viewer 4502 displays a series of data over time.The time series viewer 4502 generates performance characteristics forperformance elements, including sectored performance characteristics forsectored performance elements, based on selected performance levels forperformance attributes. The time series viewer 4502 generates theperformance characteristics and performance elements in geographicrelation to other performance elements having other performancecharacteristics and in geographic relation to geographic elements. Thetime series viewer 4502 extends the ability to visualize datageographically by adding to spatial dimensions the time dimension.

The time series viewer 4502 may be enabled by selecting the time seriesviewer button 4048 on the menu selector 4010. Upon selecting the timeseries viewer button 4048, a pull-down menu enables a user to select aperiod of time for which data may be viewed, including daily, weekly,monthly, yearly, or some other time granularity. In the example of FIGS.45A-45B, a monthly time granularity is selected.

The time series viewer 4502 includes time series controls, including aspeed control slider 4504 and playback controls 4506. The speed controlslider 4504 may be used to set the playback speed in a range betweenslow to fast. The playback controls 4506 may include a play button 4508,a pause button 4510, a reverse button 4512, and a forward button 4514.Further, the playback controls 4506 may include a playback slider 4516.Other time series controls, including other playback controls andsliders, may be included. Using the reverse and forward buttons 4512 and4514, the maps can be advanced backward and forward one time unit at atime, including one day at a time. Also, the rubber band zoom may beused to enlarge an area of interest.

When the time series viewer 4502 plays back from a starting pointforward in a period of time, the performance characteristics for theperformance elements, including sectored performance characteristics forsectored performance elements, if any, may change depending on selectedperformance levels for selected performance attributes and actual datafor the system. For example, FIG. 45A depicts data for a first day of amonth, and FIG. 45B depicts data for a third day of the month. Thesectored performance characteristics for the sectored performanceelements for the cells 4050, 4058, 4060, and 4062 change between thedata depicted in FIG. 45A and the data depicted in FIG. 45B. Theperformance characteristics, in this case the colors for the performanceelements, change from day to day showing normal, moderate, and excessiveusage for each cell from one day to the next.

The user may view the entire selected time granularity or use theplayback controls to select a portion of the selected time. In theexample in FIGS. 45A and 45B, the time for the data generated for theperformance characteristics of the performance elements are depicted inthe lower left corner of the map area 4518. Using the time series viewer4502, pockets of cell traffic and congestion may be identified overtime.

The data viewer may be used for multiple types of data and multipletypes of networks. As used herein, the term “network” may identify oneor more different types of geographic areas in which one or more typesof data are to be depicted. For example, a network may include an oil orgas industry network configured to identify one or more oil wells. Ifcircles and concentric rings are used to depict locations of oil wellsand performance elements having performance characteristics forperformance levels of performance attributes, an inner circle mayidentify a well or well classification, a first concentric ring mayidentify a monthly well production, and a second concentric ring mayidentify a well depth range. A color from a color swatch may beassociated with each circle and concentric ring to identify performancecharacteristics.

For example, a well may be classified as a field extension well, adevelopment well, or a wildcat well. A performance characteristic may beassociated with each of the types of wells, including green for thefield extension well, yellow for the development well, and red for thewildcat well. Alternately, a shade of gray, cross-hatching, or someother performance characteristic may be identified for the performanceelement.

Similarly, if a first concentric ring is used to identify monthly wellproduction, green may be associated with production below ten billioncubic feet (BCF), yellow may be associated with production between tenand thirty BCF, and orange may be associated with production above 30BCF. Similarly, cross-hatching, shades of gray, or some otherperformance characteristic may be used for a performance element.

Additionally, for a performance element identifying the well depthrange, blue may be associated with well depth of between fifteenthousand and twenty-five thousand feet, green may be associated for welldepth of between ten thousand and fifteen thousand feet, red may beassociated with well depth between six thousand and ten thousand feet,and white may be associated with a well depth of between zero and sixthousand feet.

In another example, performance elements may be applied to dailyshipping costs versus daily profit versus daily customer volume atspecified discount stores across the nation. Color coded concentriccircles can enable a user to rapidly visually analyze historical datafor a day, month, quarter, year, or some other unit of time. Filteringand rendering capabilities (i.e. the performance elements) can enable auser to pinpoint stores having high shipping costs but low profit orhigh customer volumes and low profit. Other examples exist.

The present system and method provide geographic map features withnetwork elements and performance elements, including sectoredperformance elements, to represent different levels of attribute dataassociated with the various types of networks, including communicationnetworks, oil/gas industry networks, store networks, and other types ofnetworks. The multiple performance elements, in one case concentriccircles, are unique in that performance characteristics, such as variedcolors, are rendered dynamically from dynamically changing data, and therendering data attributes (i.e. selected performance levels for selectedattributes) can be selected dynamically by an end user. The dynamicrendering of data as feature attributes provides the ability to render amap of a geographic area representing feature data at any point in timethat is available in a database. This enables the ability to view datafrom an hour, week, month, quarter, year, or some other time period.Moreover, because sectored performance elements may be used, and thesectored performance elements may be of any shape or designation,including stacked polygons, multiple data sets simultaneously may beviewed for a single network element or network element area.

Those skilled in the art will appreciate that variations from thespecific embodiments disclosed above are contemplated by the invention.The invention should not be restricted to the above embodiments, butshould be measured by the following claims.

What is claimed is:
 1. A system for managing a network, the systemcomprising: generating, by a processor, display elements for display ona map, the display elements comprising: geographic elements each havingat least one geographic characteristic; one or more trouble tickets eachrepresenting a reported problem and that is displayed on the map using afirst shape; at least one trouble area that is automatically created inresponse to a new trouble ticket being created within a specified rangeof a specified number of other trouble tickets and that is displayed onthe map using a second shape; a plurality of network elements eachhaving at least one network characteristic and that are displayed on themap using a third shape that is configured to vary depending on a valueof a corresponding performance attribute of that network element; and aseparate performance element for each of the plurality of networkelements, each performance element comprising another shape for displayon the map surrounding the third shape and having at least oneperformance characteristic and having a position that is configured tovary depending on the value of the corresponding performance attribute;and receiving, by the processor, selection of one of a network elementfrom the plurality of network elements displayed on the map and atrouble ticket from the one or more trouble tickets displayed on the mapfor navigating through network data and geospatial data.
 2. The systemof claim 1 wherein a plurality of performance elements are generated fordisplay for each network element of the plurality of network elements.3. The system of claim 1 wherein the network comprises at least onemember of a group consisting of a communication network and anotherbusiness network.
 4. The system of claim 1 wherein the network comprisesat least one member of a group consisting of an oil network, a gasnetwork, a store network, a packaging network, and another businessnetwork.
 5. The system of claim 1 wherein the at least one performancecharacteristic for at least one performance element comprises at leastone member of a group consisting of a color, a shade, a cross-hatch, afill, and the shape.
 6. The system of claim 5 wherein at least one otherperformance characteristic for the at least one performance elementcomprises at least one member of a group consisting of a second color, asecond shade, a second cross-hatch, a second fill, and a second shape.7. The system of claim 5 wherein at least one other performancecharacteristic for at least one other performance element comprises atleast one member of a group consisting of a second color, a secondshade, a second cross-hatch, a second fill, and a second shape.
 8. Thesystem of claim 1 wherein at least one performance element comprises atleast a portion of at least one member of a group consisting of aconcentric ring, a pie-shape, a circle, and a polygon.
 9. The system ofclaim 1 wherein a plurality of the performance elements comprise atleast a portion of at least one member of a group consisting of aplurality of stacked polygons and a plurality of concentric rings. 10.The system of claim 1 wherein the system further is configured togenerate for display at least one member of a group consisting of a hotspot, a coverage area, the trouble ticket relative to at least onegeographic element, and the trouble ticket relative to at least onenetwork element.
 11. A method for managing a network, the methodcomprising: generating, by a processor, display elements for display ona map, the display elements comprising: geographic elements each havingat least one geographic characteristic; one or more trouble tickets eachrepresenting a reported problem and that is displayed on the map using afirst shape; at least one trouble area that is automatically created inresponse to a new trouble ticket being created within a specified rangeof a specified number of other trouble tickets and that is displayed onthe map using a second shape; a plurality of network elements eachhaving at least one network characteristic and that are displayed on themap using a third shape that is configured to vary depending on a valueof a corresponding performance attribute of that network element; and aseparate performance element for each of the plurality of networkelements, each performance element comprising another shape for displayon the map surrounding the third shape and having at least oneperformance characteristic and having a position that is configured tovary depending on the value of the corresponding performance attribute;and receiving, by the processor, selection of one of a network elementfrom the plurality of network elements displayed on the map and atrouble ticket displayed on the map from the one or more trouble ticketsfor navigating through network data and geospatial data.
 12. The methodof claim 11 further comprising generating for display a plurality ofperformance elements for each network element of the plurality ofnetwork elements.
 13. The method of claim 11 further comprisinggenerating the display elements for display wherein the networkcomprises at least one member of a group consisting of a communicationnetwork and another business network.
 14. The method of claim 11 furthercomprising generating the display elements for display wherein thenetwork comprises at least one member of a group consisting of an oilnetwork, a gas network, a store network, a packaging network, andanother business network.
 15. The method of claim 11 further comprisinggenerating the at least one performance characteristic for at least oneperformance element comprising at least one member of a group consistingof a color, a shade, a cross-hatch, a fill, and the shape.
 16. Themethod of claim 15 further comprising generating at least one otherperformance characteristic for the at least one performance elementcomprising at least one member of a group consisting of a second color,a second shade, a second cross-hatch, a second fill, and a second shape.17. The method of claim 15 further comprising generating at least oneother performance characteristic for at least one other performanceelement comprising at least one member of a group consisting of a secondcolor, a second shade, a second cross-hatch, a second fill, and a secondshape.
 18. The method of claim 11 further comprising generating at leastone performance element comprising at least a portion of at least onemember of a group consisting of a concentric ring, a pie-shape, acircle, and a polygon.
 19. The method of claim 11 further comprisinggenerating a plurality of the performance elements comprising at least aportion of at least one member of a group consisting of a plurality ofstacked polygons and a plurality of concentric rings.
 20. The method ofclaim 11 further comprising generating for display at least one memberof a group consisting of a hot spot, a coverage area, the trouble ticketrelative to at least one geographic element, and the trouble ticketrelative to at least one network element.
 21. A system for managing anetwork, the system comprising: generating, by a processor, displayelements for display on a map, the display elements comprising: at leastone geographic element; at least one trouble ticket representing areported problem and that is displayed on the map; at least one networkelement having at least one network characteristic and that is displayedon the map using a first shape that is configured to vary depending on avalue of a corresponding performance attribute of the network element;and at least one performance element, the at least one performanceelement comprising a concentric shape displayed concentrically aroundthe first shape of a separate corresponding network element from the atleast one network element displayed on the map and having at least oneperformance characteristic and having a position, the performancecharacteristic corresponding to at least one performance attribute, theat least one performance characteristic and the position varying basedon a performance level of the performance attribute and indicating theperformance level of the performance attribute; and receiving, by theprocessor, selection of one of a network element from the at least onenetwork element displayed on the map and a trouble ticket from the atleast one trouble ticket displayed on the map for navigating throughnetwork data and geospatial data.
 22. A method for managing a network,the method comprising: generating, by a processor, display elements fordisplay on a map, the display elements comprising at least onegeographic element; at least one trouble ticket representing a reportedproblem and that is displayed on the map; at least one network elementhaving at least one network characteristic and that is displayed on themap using a first shape that is configured to vary depending on a valueof a corresponding performance attribute of the network element; and atleast one performance element, the at least one performance elementcomprising a concentric shape displayed concentrically around the firstshape of a separate corresponding network element from the at least onenetwork element displayed on the map and having at least one performancecharacteristic and having a position, the at least one performancecharacteristic corresponding to at least one performance attribute, theat least one performance characteristic and the position varying basedon a performance level of the performance attribute and indicating theperformance level of the performance attribute; receiving, by theprocessor, selection of one of a network element from the at least onenetwork element displayed on the map and a trouble ticket from the atleast one trouble ticket displayed on the map for navigating throughnetwork data and geospatial data.